V12 Release

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
The "cost" for the blockchain is the actual size of the transaction - the larger your tx the greater the "cost" (the fee). To account/predict tx fee you need to calculate the size of the raw tx. You can try to get into blockchain for free (there is a small cap for it) but keep in mind that there is no incentive for miners to include such txes so it might never be included in blocks at all.
This is where my tech knowledge of the blockchain starts to fail me. So what determines the size of a tx? Isn't it the sum of vins + vouts?
So if you create a feature to consolidate all your inputs after each tx through a persistent change address, every subsequent tx will have a much lower kb weight
Obviously this has other implications and not ideal for all, but just trying to figure this out.

.
 

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
This is where my tech knowledge of the blockchain starts to fail me. So what determines the size of a tx? Isn't it the sum of vins + vouts?
So if you create a feature to consolidate all your inputs after each tx through a persistent change address, every subsequent tx will have a much lower kb weight
Obviously this has other implications and not ideal for all, but just trying to figure this out.

.
The size of tx is the size of the raw data structure filled with your data, it has (almost) nothing to do with values. ("almost" - because different value could take different amount of memory/space to store them)
I would recommend to read more about txes:
https://bitcoin.org/en/developer-guide#transactions - to get the idea
https://bitcoin.org/en/developer-examples#transaction-tutorial - to see some real world examples
https://bitcoin.org/en/developer-reference#raw-transaction-format - to dive deeper into format

Having a persistent change address could help you to eliminate situations where you would have many inputs for some txes but it is highly not recommended use case because of the huge damage it brings to anonymity.
 
  • Like
Reactions: yidakee

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
UdjinM6 Gotcha! Anonymity in this case would not be essencial. Anyway, thank you very much for taking the time to answer and the material to review!
 

Bridgewater

Well-known Member
Foundation Member
Dec 14, 2014
183
164
203
I have a masternode stuck at block 415399.

The debug.log is full of these messages:
Code:
2016-02-13 09:18:13 ProcessMessage(headers, 162003 bytes) FAILED peer=42
2016-02-13 09:18:13 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:13 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:13 ProcessMessage(headers, 162003 bytes) FAILED peer=5
2016-02-13 09:18:14 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:14 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:14 ProcessMessage(headers, 162003 bytes) FAILED peer=29
2016-02-13 09:18:15 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:15 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:15 ProcessMessage(headers, 162003 bytes) FAILED peer=8
2016-02-13 09:18:15 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:15 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:15 ProcessMessage(headers, 162003 bytes) FAILED peer=3
2016-02-13 09:18:20 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:20 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:20 ProcessMessage(headers, 162003 bytes) FAILED peer=6
Will -reindex fix this or is there another problem?
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
I have a masternode stuck at block 415399.

The debug.log is full of these messages:
Code:
2016-02-13 09:18:13 ProcessMessage(headers, 162003 bytes) FAILED peer=42
2016-02-13 09:18:13 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:13 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:13 ProcessMessage(headers, 162003 bytes) FAILED peer=5
2016-02-13 09:18:14 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:14 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:14 ProcessMessage(headers, 162003 bytes) FAILED peer=29
2016-02-13 09:18:15 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:15 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:15 ProcessMessage(headers, 162003 bytes) FAILED peer=8
2016-02-13 09:18:15 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:15 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:15 ProcessMessage(headers, 162003 bytes) FAILED peer=3
2016-02-13 09:18:20 ERROR: AcceptBlockHeader : block is marked invalid
2016-02-13 09:18:20 ERROR: invalid header received 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2
2016-02-13 09:18:20 ProcessMessage(headers, 162003 bytes) FAILED peer=6
Will -reindex fix this or is there another problem?
Maybe this is worth a try first:

try "reconsiderblock 0000000000056aa1260c0eeab2bf21da258e1a528ba6c9a20a739b70d7330af2" from the console