Hi, it looks like you’re not connected to the testnet. Could you please post the contents of epoch.yaml and the output of curl localhost:3013/v2/status.
I see you’re running v0.20 and testnet is currently running v0.21, please try installing and run epoch v0.21.
Epoch versions are usually not backward compatible (yet), so you should make sure you’re always running the latest version if you want to connect to the testnet. Also please note that, it’s expected to release v0.22 tomorrow midday if everything goes well, so we might need to install that to connect to testnet.
You’re probably not connected to other peers and mine on your own.
There is no separate update procedure as of now, you have to install the new version in a new directory. Don’t forget to stop the old version node, before running the new one.
You can find more about version 0.21 in the release notes.
Elixir node is parallel implementation of the protocol, however it’s couple of versions behind the erlang node, so you won’t be able to connect to the testnet yet. @philipp.chain Can share more details about it.
Hello yeqinfu, I am the project manager of the elixir team. Development in the elixir project started a lot later than epoch and our team has a very different structure and experience level. Currently we work to match the aeternity 0.16. specification, we plan to have this working within the next weeks.
Afterwards the plan is to catchup with the latest aeternity release to this time, 0.23 maybe. I assume this will take 2-3 months, so in total we are about 3 months behind our core-development team when it comes to being ready for mainnet release.
The aetenity erlang implementation should definitely be seen as reference implementation, with the elixir one as experimental alternative for now, but sometime after mainnet the elixir version will be ready and up-to-par with erlang.
We don’t expose API docs on node as of now, you can see the latest release api docs at: https://aeternity.github.io/epoch-api-docs/ (your link points to development version).
Only the JSON schema is published on each node and can be accessed at http://node_address:port/api for example: http://52.10.46.160:3013/api