diva.exchange @social@social.diva.exchange

@geinsios diva blockchain is the "DEX" - the logic is distributed all over the network (there is really no central component - at least in our code from github.com/diva-exchange).

Someday there will be a useable user interface (current raw prototype: github.com/diva-exchange/diva) for demonstration purposes available (on testnets).

This might then inspire other use cases developed by other people.

Thank you for all your important tests! It helps us to better understand different environments.

@geinsios If you have doubts that you are part of any given diva network:

1. check your local /about page using the API, like - by default - curl localhost:17468/about
2. there you will see (and everybody else in the network) your public key
3. use any other instance of the network and check whether your public key is part of their node list.

Example, using the testnet: go to https://testnet.diva.exchange and search for your public key. If it's there, your node is a network member.

@geinsios That's normal. The log (at least on the default logging level) shows only "problems". The current height is now 83 (6/dec/2022 10:16 CET)

@geinsios This looks quite normal to me. Reason: this is an I2P network - sometimes communication between nodes fails. BTW: this is why diva needs a distributed ledger - the network itself is unstable [=costs of anonymity] but the functionality of diva (=exchanging digital values between peers) still requires reliability and resilience. You can check the latest block by using the API of your local chain (https://github.com/diva-exchange/divachain#get-blocklatest) and compare it with https://testnet.diva.exchange. Use curl for that.

@geinsios during the startup of the chain, it is normal that there are error messages. Reason: the i2p network is not stable in the beginning and there are quite some packages lost. Nevertheless, after a few minutes, the sync works usually. Check your local explorer or the local chain api using curl. Also the public testnet.diva.exchange explorer will help, because there you see your public key.

@geinsios Here is the starting point for you:

https://github.com/diva-exchange/diva-dockerized

this will work within your vps (because i2pd is working within your vps).

@geinsios cool - i2pd is working. Well done. 👍

Now, you can, if you like, try the complete project (please first check github.com/diva-exchange/diva-dockerized - there are for sure some new commits). 😀

@geinsios What about "curl 127.0.0.1:7070" ? this should output the status page within your terminal (as html, so a bit difficult to read - but you'll figure it out).

So with curl you will know whether i2pd is properly working within your vps (uptime, firewall status, connections to other peers etc.) - this would be step one, before using diva-dockerized as a whole.