elective-stereophonic
elective-stereophonic
Batch transactions: Request for comments singapore
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Nxt Client: Nxt 1.11.15

Author Topic: Batch transactions: Request for comments  (Read 2228 times)

Zahlen

  • Full Member
  • ***
  • Karma: +26/-4
  • Offline Offline
  • Posts: 228
    • View Profile
Batch transactions: Request for comments
« 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
Logged

LocoMB

  • Hero Member
  • *****
  • Karma: +101/-37
  • Offline Offline
  • Posts: 751
    • View Profile
Re: Batch transactions: Request for comments
« Reply #1 on: September 28, 2014, 01:26:51 pm »

hey thanks! I will forward it to a few other guys also!
Logged
TOX
90E54E5B5213290EE616D425CADC473038CFABFA53C913271AA8559D1937DC4AF3A354A9E4E5

LocoMB

  • Hero Member
  • *****
  • Karma: +101/-37
  • Offline Offline
  • Posts: 751
    • View Profile
Re: Batch transactions: Request for comments
« Reply #2 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.
Logged
TOX
90E54E5B5213290EE616D425CADC473038CFABFA53C913271AA8559D1937DC4AF3A354A9E4E5

Zahlen

  • Full Member
  • ***
  • Karma: +26/-4
  • Offline Offline
  • Posts: 228
    • View Profile
Re: Batch transactions: Request for comments
« Reply #3 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)
Logged

Zahlen

  • Full Member
  • ***
  • Karma: +26/-4
  • Offline Offline
  • Posts: 228
    • View Profile
Re: Batch transactions: Request for comments
« Reply #4 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?
Logged

printshop

  • Hero Member
  • *****
  • Karma: +123/-317
  • Offline Offline
  • Posts: 1004
    • View Profile
Re: Batch transactions: Request for comments
« Reply #5 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.

Sebastien256

  • Hero Member
  • *****
  • Karma: +169/-24
  • Offline Offline
  • Posts: 2823
  • ^LOOK UP^ = Nxt community!
    • View Profile
Re: Batch transactions: Request for comments
« Reply #6 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.
Logged
Please drop your ideas concerning Nxt and/or NRS in this topic -> List of feature request for Nxt and/or NRS (with the full list in OP).

Peter2516

  • Hero Member
  • *****
  • Karma: +132/-27
  • Offline Offline
  • Posts: 1235
    • View Profile
Re: Batch transactions: Request for comments
« Reply #7 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?
Logged
 

elective-stereophonic
elective-stereophonic
assembly
assembly