[snowblossomcoin/snowblossom] Issue closed by fireduck64

@Eric has joined the channel

We need to do this anyways. The TransactionUtil.makeTransaction will a bunch of parameters needs improvement. So the new one will have a configuration object that specifies all the parameters. Options to support: • Broadcast or just return tx data • Sign or not • Split change if larger than X • Change (explicit addresses, random address from wallet, fresh address (default)) • Inputs (explicit list of candidates, confirmed then pending (default), confirmed only) • Fee (explicit, based on node recommendation) Should be supported in java library and via json rpc

Need facility to sign a transaction. This allows multisig use cases as well, since the partially signed transaction can be handed around.

probably json rpc callback. Register with node?

make sure the access functions are accessible via jsonrpc.

@Eric can you give me an idea of your normal flow? Transaction wise, snowblossom is just like bitcoin.

@bitbumper has joined the channel

Eric's gotta run but I can take the question, hope it's cool that I invited myself. I write our coin relay software.

Not sure what you mean by normal flow? Our relays are setup as a set of tasks that get run periodically. We have tasks like ScanDespoits, ConfirmDeposits, etc.

Do you sweep deposits into a pool?

Not as a matter of routine, we just construct our withdraw TXs from available unspents.

Bitcoin core can get slow with 1000+ UTXOs, so we occasionally run sweeps as a maintenance task.

Got it

So you need to make sure the change from that tx doesn't hit a deposit address.

Yeah, we have a concept of "internal" addresses that can be cold storage, change, etc. Deposits to these addresses are monitored but do not credit user accounts.

Makes sense.

Can you take a look at issue 108?

It is notes for new transaction create library

I want to make sure it covers your needs

Sure, let me take a look

Yeah looks like it would have everything we need. A few thoughts: • If we let the node pick the fee, it would be nice to have the fee information in the return payload for logging/analytics • We would likely be giving an explicit list of UTXO candidates and asking for an unsigned transaction • Split change is a nice feature, although not strictly needed.

Cool