Bitsler update
-
Hi @Lexicon any update from Bitlser about Burst exploit you wanted you warn them about?
-
@Ip85 nope they never bothered to contact me. i wanted to tell them to wait until after we release the new wallet that fix's said issue but i guess that aint going to happen.
-
@Lexicon said in Bitsler update:
@Ip85 nope they never bothered to contact me. i wanted to tell them to wait until after we release the new wallet that fix's said issue but i guess that aint going to happen.
For those of us not in the inner circle, what was/is the issue?
-
@rds I am not in the inner circle.I am a mere miner with 20TB and a bag of coin.I just had a look on Bitlser twitter for a Burst implementation update and saw @Lexicon tweet.
-
A severe transaction flood with for example 50k transactions (max I have seen was 160k) will delay all other transactions with the same or lower fee made afterwards (backlog).
And
The nodes with the current software version have performance issues in this extreme case, which leads pools to go out of sync, which leads to transactions being unconfirmed and rejected in this time frame.
Good news is that a new wallet software version is being build which solves both issues. Also it got more expensive to send so many transactions the last months...
-
@daWallet Any ETA on when this version of the wallet will be finished? I think we can assume that when Bitlser will start using B there will be shitloads of transactions and it will happend quite soon.
-
@Ip85 said in Bitsler update:
@daWallet Any ETA on when this version of the wallet will be finished? I think we can assume that when Bitlser will start using B there will be shitloads of transactions and it will happend quite soon.
currently theres no eta. it could be a few weeks yet.
we are currently testing transactions over the testnet and making more changes.
dawallets highlighted what i'm worried about.
when these transaction floods happened last time it caused the casino to go negative a load and all the pools to also go negative of around 30-150k per pool. due to roll backs when forks reach a consensus. it also badly messed up all the block explorers and anything that stored data out of the chain would be incorrect and require resyncing
-
@Lexicon Thank you.Keep on good work gents!
