Nxt Forum

NxtForum Archive => Defunct Committees => Community Funding Committee (CFC) => Technical Development Fund Committee => Topic started by: Zahlen on September 27, 2014, 03:04:36 pm

Title: Batch transactions: Request for comments
Post by: Zahlen on September 27, 2014, 03:04:36 pm
I wrote up an idea about batching together multiple transactions from the same sender into one transaction to save space on repeated fields. I put it up in the Nxt Improvement Proposal subforum, but it hasn't received much attention. Posting this to get more attention, hope you guys can comment on it :)

https://nxtforum.org/nxt-improvement-proposals/batch-transactions
Title: Re: Batch transactions: Request for comments
Post by: LocoMB on September 28, 2014, 01:26:51 pm
hey thanks! I will forward it to a few other guys also!
Title: Re: Batch transactions: Request for comments
Post by: LocoMB on October 02, 2014, 01:09:06 pm
Jean-Luc commented on this:


Adding transaction types that do payments to multiple recipients at once will happen, e.g. for asset dividends. Some other specific transaction types can be optimized to do multiple changes at once, e.g. allow a seller to update many product prices in one transaction. But a generic feature to bundle multiple transactions into one, where each internal transaction is still considered a separate transaction, will not save much space or processing, as those transactions still have to be unpacked and take multiple rows in the database, otherwise you can't run queries on them or need to handle them as a special case. The increase in code complexity in my opinion exceeds any potential savings.
Title: Re: Batch transactions: Request for comments
Post by: Zahlen on October 02, 2014, 03:18:27 pm
Adding transaction types that do payments to multiple recipients at once will happen, e.g. for asset dividends. Some other specific transaction types can be optimized to do multiple changes at once, e.g. allow a seller to update many product prices in one transaction.

WOOHOO! :D Time to party!

Thanks jean-luc, l8orre and all the core devs.

(All you guys paying dividends, feel free to gimme tips :D)
Title: Re: Batch transactions: Request for comments
Post by: Zahlen on October 02, 2014, 03:23:15 pm
Does jean-luc have estimate figures of how much is saved? E.g. space used on the blockchain by 100 separate Nxt transfers, vs all of them batched together like this? And consequently how much the fee can be reduced for batch txs?
Title: Re: Batch transactions: Request for comments
Post by: printshop on October 29, 2014, 07:13:04 pm
Does jean-luc have estimate figures of how much is saved? E.g. space used on the blockchain by 100 separate Nxt transfers, vs all of them batched together like this? And consequently how much the fee can be reduced for batch txs?

When I pay dividends every week it costs me 40 or so NXT. Moving to monthly dividends saves me over 1,000 NXT a year. That's actually a lot of NXT.

Frankly I think that the client should be able to construct many transactions and send them off one by one. Packaging them together isn't necessary, but rather, reducing fees for that kind of transaction. If the client could just batch off to every asset holder, but at 0.1 per transaction, that would seem to make more sense to me than writing special code to pack and unpack transactions.

Actually even if the fee wasn't lowered, just having the client auto-construct the payments would be a huge time saver.
Title: Re: Batch transactions: Request for comments
Post by: Sebastien256 on October 29, 2014, 07:15:48 pm
It is plan by the community to reduce the Nxt fee once after the voting system is in place. This will happen.
Title: Re: Batch transactions: Request for comments
Post by: Peter2516 on October 29, 2014, 08:45:33 pm

just having the client auto-construct the payments would be a huge time saver.

Doesn't the Dividend+ option in the wallet do exactly that?
elective-stereophonic
elective-stereophonic
assembly
assembly