Only tech topics about Waves: dev tools, libs, RIDE, dApps, Nodes Github: http://tiny.cc/github-waves IDE: https://ide.wavesplatform.com/ Online Course: https://stepik.org/course/54415 StackOverflow: #wavesplatform Jobs: https://t.me/wavesridejobs
We are trying to represent a transaction that already exists without any issues. The problem is that it gives an error because of the proof
https://testnet.w8.io/tx/GPTg7r3JCYaXbvqk6LacVMcJy5ygzfa5wZZop2dkJWJZ
Feel free to use serializer from a node (https://nodes.wavesnodes.com/api-docs/index.html#/utils/serializeTx) to get valid bodyBytes
Читать полностью…Hello,
Has anyone encountered the error “State check failed. Reason: Proof doesn’t validate as signature for <TX>”?
We are building our tool for the L1 bridge to L0 using Python and PyWaves. So far, everything was fine, but now we are facing a problem with the proof.
The JSON looks fine, but we still face the issue
*Fixed; If you still get an error for besu in the logs, you may need to restart the Node; If updating/downloading from scratch, never stop or restart Node until the update is finished!
Читать полностью…Progress in besu logs is slowly progressing!
Читать полностью…What kind of errors appear periodically?
Читать полностью…For the development of the project and the ecosystem, I think there needs to be an alternative UI or app launched as soon as possible.
Читать полностью…https://app.tsunami.exchange/trade
Читать полностью…Read the logs, you synced to a block number 1072363, but the chain also progressed while you syncing so your node need to catch up 51373 new blocks. Your node still syncing but not from block number 0, but from 1072363.
Читать полностью…I didn't touch anything, but synchronization started at 0%
Читать полностью…idk how fast but after 80% things are very slow
Читать полностью…Don't stop it! This only synchronizes blocks created since the start of the sync...
Читать полностью…No idea why, but happen same on us
Читать полностью…First arg should be string not binary
Читать полностью…To use new deployment (Waves v1.5.6-133-g66833ec Blockchain Id: T ) use these;
docker compose down
docker compose pull
docker compose up -dЧитать полностью…
⚠️ There is currently an ongoing problem on the L1 (UNIT 0) network, the cause of which has not yet been determined; do not change any of your settings, just wait!
Читать полностью…I have no idea, but if you see a progress in logs, there is a chance
Читать полностью…Tsunami team moved to TON, better go ask them why situation currently are like this
Читать полностью…@NoahWaves
@ArtyomWaves
@emmawaves
@NoahWaves
@petrwaves
Tsunami's UI website has been unable to display properly for nearly a month...
Читать полностью…Very disappointing! It was 99.96 or 99.97% Almost everything was synchronized...
Читать полностью…When it’s full synchronised it’s possible to stop the node and tar.gz the data folder. Anyone can host the archive?
Читать полностью…I did the same 😂 Luckily it was finished in 32 hours
Читать полностью…we restarted to "fix" the error... Well synch started from 0%
Читать полностью…I thought I was the only one having such problems...
Читать полностью…About 150 hours have passed. Besu was 99.96% synchronized. Then these errors started appearing and synchronization started again...
Читать полностью…