smartbch/docs

Official Documents of smartBCH

docs's Issues

Incorrect regtest network settings in docs/testnets.md

I'm adding the smartBCH amber testnet (which works fine) and also adding the corresponding BCH regtest network.

The remote node for the BCH regtest (addnode=47.115.171.70:28331) is incorrect. It doesn't connect.

Using the data provided in https://github.com/smartbch/artifacts/releases/download/v0.0.4/dot.smartbchd.tgz, I can see there is a node for rpc calls (mainnet-rpc-url = "http://34.150.125.124:8332"). I was able to connect to that IP, using port 8331, and downloading a blockchain.

The latest block for this node is:

{
  "version": 20215000,
  "protocolversion": 70012,
  "blocks": 646365,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 4.656542373906925e-10,
  "testnet": false,
  "relayfee": 0.00001000,
  "errors": "WARNING: check your network connection, 0 blocks received in the last 4 hours (24 expected)"
}

Block 646365 has hash 00000047b24c9d04b13c14eea1f862353601933c7b078f1909f74c0647026cf0, and has the following header:

{
  "hash": "00000047b24c9d04b13c14eea1f862353601933c7b078f1909f74c0647026cf0",
  "confirmations": 1,
  "height": 646365,
  "version": 536870912,
  "merkleroot": "3c7612c012dcc45fa59a1d38dbfe47c1fcd7da44f846153dbd6678f6574009d5",
  "time": 1629091057,
  "mediantime": 1629090847,
  "nonce": 346310912,
  "bits": "207fffff",
  "difficulty": 4.656542373906925e-10,
  "chainwork": "000000000000000000000000000000000000000000000000000000000013b9bc",
  "previousblockhash": "0000003073c5cd4019344b7d80547558997aa228576a1092831479e84222d709"
}

The time translates to Monday, August 16, 2021 5:17:37 AM GMT.

It's September 9th today, so many more blocks should have been created.

Being behind on the underlying BCH network results in smartBCH warnings "commit is for a block we do not know about". It seems to work regardless (which by itself is a bit surprising), but it is not right.

What is the address of a working, up to date, node that I can connect to?

cc_covenant in sha-gate.md has .split(82), unlike (41) in cc_covenant_v0.cash

Line 24 of the appendix source code here & here should probably have .split(41) instead of .split(82). That's the only difference to cc_covenant_v0.cash.

I'm using the hex as an example for a Script decoder (Electron-Cash) plugin I've released. I only noticed the 0x29 vs 0x52 discrepancy today.

Documents missing upgrade instructions for SmartBCH

Documents for installing on mainnet are clear but it doesn't have instruction for upgrading.
In the first paragprah of current installation documents it has:
rm -rf .smartbchd
so trying to upgrade using those instruction will cause to remove all data and configurations.

Please provide a method for upgrading SmartBCH safely without losing data or configurations.