Coretime Endpoint doesn't work

polkadot-js / api

Promise and RxJS APIs around Polkadot and Substrate based chains via RPC calls. It is dynamically generated based on what the Substrate runtime provides in terms of metadata.

Apache License 2.0

1.06k stars 342 forks source link

Coretime Endpoint doesn't work #5848

Closed poppyseedDev closed 2 months ago

poppyseedDev commented 2 months ago

I'm submitting a BUG

[x] Bug report
[ ] Feature request
[ ] Support request
[ ] Other

What is the current behavior and expected behavior?

What is the motivation for changing the behavior?

The endpoint wss://rococo-coretime-rpc.polkadot.io is currently producing an assertion error. Currently you are not able to do any sort of transaction, other times (for example yesterday) this wasn't an issue and things were working fine.

Please tell us about your environment:

Version: "@polkadot/api": ">=10",
Environment:
- [x] Node.js
- [x] Browser
- [ ] Other (limited support for other environments)
Language:
- [ ] JavaScript
- [x] TypeScript (include tsc --version) ^5.3.2
- [ ] Other

TarikGul commented 2 months ago

I don't have any ROC, so I am not able to test any transactions, yet... (I will try and get some soon), but for general purposes I am seeing no issues connecting to the chain etc via the websocket URL you posted.

Can you provide some of the assertion errors so I can investigate it further?

poppyseedDev commented 2 months ago

It this error, usually it happens when there is some issue with the compilation of the node:

😞 Transaction Failed: Error: Assertion failed

poppyseedDev commented 2 months ago

@TarikGul You can use the Rococo testnet faucet -> Choose Rococo network, chain Coretime

TarikGul commented 2 months ago

Yea I was able to send a transaction fine on Rococo Coretime, used the same WS url you gave to.

TarikGul commented 2 months ago

Is this still an issue for you?

poppyseedDev commented 2 months ago

So it seems that you have to constantly have the package of polkadot.js api updated to the latest version, otherwise the metadata doesn't match up and the transactions won't go through.

Yes, you can close the issue.

TarikGul commented 2 months ago

So it seems that you have to constantly have the package of polkadot.js api updated to the latest version, otherwise the metadata doesn't match up and the transactions won't go through.

Not the case, (almost) everything is decorated at runtime in the api based on the metadata that is fetched from the chain. I say almost because there are certain things such as RPC's, and runtime api's that are not decorated (yet).

polkadot-js-bot commented 2 months ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.