Main > Stakeholder Proposals

Careful when upgrading delegate to 0.4.25

(1/5) > >>

vikram:
[URGENT] Delegates Please Revert Upgrade!

https://bitsharestalk.org/index.php?topic=7067.msg161312#msg161312

https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432

All community members please help spread the word.

abit:
It seems that a fork occurred before expected (<1249400).
All delegates should upgrade. Other users should upgrade as well. Wish the binary releases asap.
@vikram.

svk:

--- Quote from: vikram on December 12, 2014, 04:20:44 am ---I've updated the release notes to include a note about the memory requirement: https://github.com/BitShares/bitshares/releases/tag/v0.4.25

--- End quote ---

This doesn't appear to be true for reindexing and syncing, I've successfully reindexed and sync my seednode which has 512mb RAM and 4gb swap.

I compiled it on my personal computer which has 8gb of RAM so no issues there.

ripplexiaoshan:
I am using 2GB VPS, and it seems fine for both compiling and running, but my delegate keeps missing blocks while the wallet is up，according to bitsharesblocks.com.

emski:
0.4.24 instances report a lot of duplicate transactions when blockchain_use_forks is used. Is it the same with you ?

Navigation

[0] Message Index

[#] Next page