honeycrypto

We can solve it on UI side in 2 possible ways: 1) Make transactions from 'Send' tab to be CALL with non zero values instead of current TRANSFER type. So...

dinc, these are UI changes, so both 1 and 2 should be implemented by all wallet, extension etc devs (ping @witoldsz what do you think?)

@fenghaoming there are `/local-call` and `/local-create` interfaces in API v2.4.0 You need to enable API server in `config/semux.properties` and then you can find specs in swagger explorer at this address:...

This is a great proposal and we were discussing this many times in Discord. @victorx716 I think there is no drama about 1.4.0 release, validators have been warned that the...

@semuxgo so the proposed config will be like ``` api.enabled = true api.username = secret1 api.password = secret2 api.public = account, blockchain, delegate, tool # any non public is protected...

@fenghaoming take a look at devnet: https://github.com/semuxproject/semux-core/blob/master/docs/Devnet.md You can import private key and run your local private chain with 1 validator

While the storage problem is very important, this still doesn't solve all the networking problems, right? Can we consider some kind of gossiping scheme to enhance the scalability and reduce...

@witoldsz we have also #255 issue regarding delegates and fast_sync

@witoldsz in CLI wallets users must provide all the desired flags or config options on launch. That's the common practice just everywhere. ie: `./semux-cli.sh --fastsync=true --network=testnet` There must be some...