Carry Megens

Results 12 comments of Carry Megens

after these two steps, the issue was fixed, from command line in dir where extension is unpacked: npm install eventsource-parser Then Module iconv-lite was missing, which was resolved with npm...

This proposal has some impressive thinking behind it and is a great improvement on current nodes list.

Well done @StarGeezerPhil hopefuly this gets picked up soon by deso-protocol/reviewers

Fully agree with @StarGeezerPhil that this stop-gap solution will improve current state. The future direction should indeed be fully on-chain and dynamic, but until then the proposed PR will improve...

If you want a formal statement on SafetyNet standing: We fully support @StarGeezerPhil suggested numbering: 30 MyDeSoSpace (Nathan was first) 31 Focus (can still be done, launch pending) 32 SafetyNet

Medium term, a few months I read in above thread. But still this mechanism exists end of 2022. Stating deso is decentralized is then simply not true, unless this gets...

Given we are now in Proof Of Stake operation territory and have 27 validators - of which 3 only have the super majority of staked deso - a risk of...

@lazynina @diamondhands0 if you honor https://github.com/deso-protocol/core/pull/1438 this one can be skipped as @StarGeezerPhil included SafetyNet in his improved proposal. Thank you

@lazynina This is what I found in the logs, hope it helps you: {"log":"E0315 15:59:17.431221 1 pos_consensus.go:184] FastHotStuffConsensus.HandleLocalBlockProposalEvent: Error proposing block: Error processing block locally: Error proces>{"log":"I0315 15:59:17.721866 1 server.go:2338]...

BTW, we have seen a reduction in memory by setting MAX_PEERS=50 which seems to have effect on one node, but not on all. Any recommendation?