inuitwallet/Brekky

inuitwallet

@inuitwallet

Are things making a bit more sense now?

I develop in Linux. I find it much easier for python stuffstuff.

CoinGame

@CoinGame

Yeah I'm getting it

Things are a bit more organized I dhango and tied in together

In django

inuitwallet

@inuitwallet

Yeah. It is quite strict with how you should structure things which can be less flexible but, if you do it can give you a boost at the start that you may not get with flask.

Aa you add more complexity too, there are standard ways for doing most things. It normally as easy as adding something to the requirements.txt and in the installed apps in the settings. Run a migration and its good to gogo.

CoinGame

@CoinGame

Yeah i like it

Cool

CoinGame

@CoinGame

hope yall had a good weekend

wooly you wanna catch up tomorrow and tell me a bit more about the way butter is supposed to work?

are there testing interfaces for these gateways?

inuitwallet

@inuitwallet

Hi @CoinGame. Sorry, got waylaid last night and didn't see the message till now. Can't do anything tonight but will write up what I have so far on the commute tomorrow morning.

I think most of the services offer some sort of sandbox. Need to look a bit deeper at that though.

I made some good progress last night creating a seperate service that generates a HD wallet for NBT that can then be used to create addresses for the toast burn service.

It sports the private key up into two mnemonic keys which can be saved on different servers and means that spending can only take place when security has been passed and the private key regenerated.

Looking now at python libs that can read block chain data (to see new transactiins) and can sign and broadcast transactions (meaning no Nu daemon)

As I say, I'll write it up in the morning and let you take a look. Could you start thinking of potential workflows for the burn serviceservice?

CoinGame

@CoinGame

that's sick

Things have gotten a bit crazy for me. The NuBits crash caused a lot of problems. But i'll have time here and there to thought into it

inuitwallet

@inuitwallet

Yeah its all a bit crazy. I have to admit that I Dove into this dev work to avoid it a little bit :).

CoinGame

@CoinGame

that painful moment when you realize that your git pull didn't work and you just spent an hour doing something that was already done in the upstream

fml

I see your changes now

CoinGame

@CoinGame

ah you took a different approach to handling it anyway

inuitwallet

@inuitwallet

Doh! :) what bit were you taking a look at?

I only managed a gut of work yesterday but have extended pycoind to communicate with the Nu blockchain. It connects and receives addresses and blocks but doesn't download them as yet. I think the block size is different in Nu so a bit of work needed there. Could provide a seperate block Explorer when it fully works though.

CoinGame

@CoinGame

just the toggle elements thing

https://github.com/CoinGame/Brekky/compare/master...CoinGame:toggle_buy_sell?expand=1

I was playing around with burning yesterday.

thinking about the process

it shouldn't be difficult since it's just a regular transaction where the bulk of the value is the fee

CoinGame

@CoinGame

I think the more difficult part is keeping track of the accounting

do you use postgres?

inuitwallet

@inuitwallet

yup. it's all going to be Postgres based.

CoinGame

@CoinGame

Fabulous

inuitwallet

@inuitwallet

Not t don't need much more to the core service. Been playing with pycoind, trying to get it to recognise Nu blocks. If I can't get it working in the next hour or so of work I'll Park it and just use the Nu daemon to parse the blockchain to verify transactions.

CoinGame

@CoinGame

the block explorer that's open source has a nubits blockchain parser written in python

It's not th emost elegant parser, but it could be used as a reference if need be

inuitwallet

@inuitwallet

That's interesting, I wasn't aware that the current block Explorer contained any python. I had a look and it had some useful pointers. I'll definitely refer to it when I add Nu blocks to pycoind. For the time being though, I wanted to get something working so I've added functionality to collect blocks as json from nud. I've got blocks and transactions being saved, just need to sort out inputs and outputs. Then I'll add the address watching functionality and then Park that for the while. I'd like to get something working for toast so will put some models together for that.

CoinGame

@CoinGame

How do you usually handle background tasks with django?

inuitwallet

@inuitwallet

Afternoon :). For async tasks you can hook into Celery or there's the new Django-Channels which could be worth a try.

alternatively, for the block parser I have a loop which is triggered by the ready() method of the AppConfig class in the app

Thanks for your PR. it gave a good few things to think about.

I have the block parser working aside form some issues with duplicate Tx inputs. Think I need to tweak my models a little.

Once that is working (hopefully tonight) I will add in the endpoints to add an address/amount to the watch list so that the parser service ca notify toast when a Tx is made.

thinking about the method of Toast, I think each Baker should be able to specify a percentage to burn (with a minimum of 10% say) and gain profit form the other percentage. It gives more impetus to use the service

I have a few more thoughts but I'll add them to the Notes file in the repo as then they are all in the same place

CoinGame

@CoinGame

sounds like you're making big steps. I think i'll be most useful in just testing, but i'm enjoying seeing the process of building a django app

I do have a NuNet clone that we could test on. Automating making transactions to the API and burning

People

Repo info

Activity