Search results

Did you run dashmate update? I believe there are drive or tenderdash errors in the containers (you can observe them with docker ps & docker logs), it will give you more reasons why it happens I would recommend just dropping platform chain via dashmate reset --platform while services stopped

maybe you are out of sync? what is your node's platform block height? could you post more status outputs? you can also use dashmate doctor command to generate a report and send it over to the [email protected] so they can investigate

Please add debug environment to your status command, it will show you an error message in case there is a problem with request DEBUG=1 dashmate status

https://rpc.digitalcash.dev/

How do you run platform node?

Привет) Минимальный требования 4vCPU / 8 gb RAM / 200 GB Рекомендуемые требования 4vCPU / 16 gb RAM / 200 GB

I don't remember if there are documents suggesting you to use `npm update`. The difference is that `npm install` is always picking the latest version of the package, while `npm upgrade` will perform some semantical versioning from your global package list. Those two commands do almost the same...

`dashmate restart` is just an alias for `dashmate stop && dashmate start` I will check the `dashmate update`, possibly there is a chance to show what to what exactly version component have been updated

Hey folks, rc.6 is finally out and brings up few important fix and features. The most interesting feature a lot of you have been asking before, is to let dashmate update core image version itself by the command, and we eventually agreed to test this approach. Dashmate now contains tagged core...

No, removing obsolete dependencies not our case 100%, because this PR was merged into v1.0-dev, while we are working with 0.25 branch (master) I don't think you should have these problems with dashmate, at least until we decide to get Wasm DPP back in, but there aren't use cases for that...

@qwizzie Regarding your issue with SIMD, what CPU do you have on your node? The only change that happened between 0.25.13 and 0.25.15 is bumping minimum Rust version to 1.74. The error message you are receiving I believe is happening on the command init phase when WasmDPP being loaded that is...

No, unfortunately I could not reproduce your error. However I suspect one place in the code, I will confirm with the team. I'm sorry that you got an PoSe ban. Reinstalling dashmate should not really affect the pose score, because everything is stored in Docker, but reinstalling node or dashmate...

I don't know, never thought about this yet. I think we should start building other components (Drive, Dapi, etc..) and upload them in the assets first. That's more question to the DCG though Yes, you should wrap it in the "" and it should work, f.e: I'm not sure that dash-cli arguments are...

Ok, then I will try to reproduce your issue You mentioned that your have Ubuntu 20.04, what is your OS arch?

Just published a new build that fixes two bugs found by the community. @qwizzie kindly check this build out, I hope it will resolve your issue Dash Platform v0.25.16-rc.2 * Bugfix: incorrect imports caused `dashmate setup` and `dashmate update` to crash To update, donwnload a new .deb...

Thank you very much @qwizzie for the tests, I will look into that today. I checked myself and I can see there is an issue with dashmate update command, but my error message is a bit different. There were also other reports in the Discord that I am going to work today. Expect a new pre release...

Hey guys, good news! We got everything necessary for dashmate merged in today. Platform team still working on another critical issue and we have to wait with a 0.25.16 stable release. But I rolled out a release candidate build for your, so you can proceed with Core v20 masternode updates. I...

Interesting, didn't know that. Platform project was not building with Node 20 but dashmate probably could work. Yeah... that makes sense. I forgot that newer Node.JS usually breaks applications. Maybe better to stick with only one exact major Node version supported, because this happens not...

I see you use NVM, so

It's not quite correct, the release is Dashmate v0.25.15 is working. You forgot to mention that you have also updated your Node.js from 18 to 21, which broke the dashmate, not the dashmate release itself. There are no dashmate or network changes between v0.25.13 and v0.25.15, it just adds a new...