1
Technical Support / Re: Critical Bug: Blockchain sync jams at block 2821722 -- Losing New Users!
« on: July 21, 2016, 08:27:19 pm »
The BitShares 2.0 developers made the design decision that full nodes were expected to be running high-end hardware with good network connectivity. Most other coins (BitShares 0.x included) keep their indexes on disk, BitShares keeps them in memory.
The hardware doesn't have to be all that impressive.. I think you can get away with 4G if not much else is going on on the system, but it's about the minimum I'd bother trying with. I often run it on a VM with 6G that is running a few other altcoins. I usually have to shut something down if I need to do a big compile on that VM.
The protocol actually does have built-in limits on the maximum size of individual transactions and of blocks. It encourages smaller transactions by charging a per-kilobyte fee for transactions that exceed the minimum size. The "create asset" operation that seems to be causing you problems was about a megabyte, so clayop paid the base fee for creating an asset plus about 1000 times the per-kb fee. The committee can vote to change both the fees and the maximum sizes at any time, and they can vote to increase the per-kilobyte fee to make it more expensive if abuse becomes a problem. I think the max block size right now is about 2M.
The hardware doesn't have to be all that impressive.. I think you can get away with 4G if not much else is going on on the system, but it's about the minimum I'd bother trying with. I often run it on a VM with 6G that is running a few other altcoins. I usually have to shut something down if I need to do a big compile on that VM.
The protocol actually does have built-in limits on the maximum size of individual transactions and of blocks. It encourages smaller transactions by charging a per-kilobyte fee for transactions that exceed the minimum size. The "create asset" operation that seems to be causing you problems was about a megabyte, so clayop paid the base fee for creating an asset plus about 1000 times the per-kb fee. The committee can vote to change both the fees and the maximum sizes at any time, and they can vote to increase the per-kilobyte fee to make it more expensive if abuse becomes a problem. I think the max block size right now is about 2M.