EOS wallet is now live on mainnet

Hello community members,

We would like to announce that EOS wallet is now live on the mainnet and with this, the deposits and withdrawals have been enabled. Please go to your wallet and generate the new address.

After you click the “Generate New Address ” button, you will see two fields: 1. Address, and 2. Memo. The address will be common for everyone, and it is “coindeltaeos” while the memo is a numeric tag uniquely assigned to you. Its similar to XRP.

While making EOS deposits, do not forget to enter the appropriate memo.

The withdrawal fee is 0.05 EOS. Any EOS deposit will get confirmed after it becomes an irreversible transaction on EOS network, i.e., after all the block producers have approved the transaction. Usually, any transaction on the network becomes irreversible in 60 seconds.

Reason behind the delay

Warning: It’s a bit technical from here onwards.

Our whole infrastructure is in a secure private subnet with only Firewalls (and a few less critical components) in the public subnet. So, naturally we initialised the EOS node in the private subnet, but it wasn’t syncing. We tried every possible combination of configuration, switching between EOS release versions, asking help from the EOS community, none of it worked.

Security tip: All the blockchain nodes that we run are in private subnet. Private subnet disallows direct communications from the public internet.

Later, we realised the problem might be because of the private subnet. So, we initialised another EOS node in the public subnet, and voila!, it started to throw a bunch of errors periodically. It was a sigh of relief for us because at least it was responding now. We were trying with full initial sync with net_plugin. Later, we communicated out the problem with EOS devs; they suggested to use the new bnet_plugin with genesis. Upon using bnet_plugin, the node sync started, but there were a lot of connection errors, and the sync was slower than expected.

bnet_plugin.cpp:1236          on_reconnect_peers   ] attempt to connect to peer1.eosphere.io:4321
bnet_plugin.cpp:346           session              ] open session 16
bnet_plugin.cpp:1236          on_reconnect_peers   ] attempt to connect to peer.franceos.fr:4321
bnet_plugin.cpp:346           session              ] open session 17
bnet_plugin.cpp:1236          on_reconnect_peers   ] attempt to connect to node1.bp.eosindex.io:9875
bnet_plugin.cpp:346           session              ] open session 18
bnet_plugin.cpp:1236          on_reconnect_peers   ] attempt to connect to nodebnet-mainnet.eosauthority.com:19393
bnet_plugin.cpp:346           session              ] open session 19
bnet_plugin.cpp:1236          on_reconnect_peers   ] attempt to connect to seed.eoseco.com:10022
bnet_plugin.cpp:346           session              ] open session 20
bnet_plugin.cpp:848           on_fail              ] write: Bad file descriptor
bnet_plugin.cpp:848           on_fail              ] read: Operation canceled
cpp:1430          ~session             ] close session 16
bnet_plugin.cpp:848           on_fail              ] write: Bad file descriptor
bnet_plugin.cpp:848           on_fail              ] read: Operation canceled
cpp:1430          ~session             ] close session 18
bnet_plugin.cpp:848           on_fail              ] write: Bad file descriptor

Upon doing some configuration tweaks, the EOS node stopped throwing these errors and started throwing new ones 😅. For each block, we were receiving the following error:

{"id":"00add4464c462957ef71c9d47cf6d3fbc7ae88470c11b606b7e7d479b7141eec","previous":"00add445dde1f20476e964d44be20c5badc4f536a8064af73042e8629c359473"}     thread-0  fork_database.cpp:151 add 2018-08-16T08:28:24.987 thread-0   producer_plugin.cpp:310       on_incoming_block    ] 3030001 unlinkable_block_exception: Unlinkable block unlinkable block

Later, it turned out that this error was probably because of an updated version of bnet_plugin and could be ignored. So, we waited for the node to sync. And, in few days, the node got synchronized completely.

Next, we were a bit worried about EOS RPC calls, since there is no authentication mechanism in EOS for RPC calls and this was a public server. So, to add security to it, we put a reverse proxy in front of EOS Node to secure all the RPC calls.

Now you can transfer your EOS from/to Coindelta wallet without worrying about security because we are here for that.

We would like to thank the fantastic community of EOS developers for their cooperation.

This article is coming from Coindelta Devs.
Good Night!