smartcash / core-smart

SmartCash Core Wallet for SmartNodes, Exchanges, and Advanced Users

Smartcash Core

https://SmartCash.CC

Copyright (c) 2009 - 2016 Bitcoin Developers Copyright (c) 2015 - 2017 Zcoin Developers Copyright (c) 2017 - 2017 SmartCash Developers

What is Smartcash?

Smartcash is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Smartcash uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Smartcash Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Smartcash Core software, see https://smartcash.cc/

License

Smartcash Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

core-smart's Issues

Incorrect Passphrase

Seems like the v1.2.0 release broke the wallet encryption feature ... Tested on both Mac OS / Windows.

1. Downloaded SmartCash wallet
2. Launch the app after setup
3. Choose "Encrypt Wallet..."
4. Enter passphrase: "simple" (no quotes)
5. Wallet shows dialogs and momentarily shuts down
6. Re-launch application, choose "Change Passphrase..."
7. Enter "simple" (no quotes) as the old passphrase, and "password" twice as the new passphrase
8. Observe the wallet giving "Incorrect passphrase"
9. Try the exact same steps through the Debug Console.
10. Same result, "Incorrect passphrase"

Sync issues

wallet synced up until last block as per block explorer
though still giving error on getblocktemplate
error -10: smartcash is syncing with network...

getinfo
{
"version": 1020300,
"protocolversion": 90026,
"walletversion": 130000,
"balance": 0,
"blocks": 548414,
"timeoffset": 0,
"connections": 8,
"proxy": "",
"difficulty": 61347.85184762,
"testnet": false,
"keypoololdest": "2018-07-09 10:11:01 +0300",
"keypoolsize": 199,
"paytxfee": 0,
"relayfee": 0.001,
"errors": ""
}

getblocktemplate
error -10: smartcash is syncing with network...

Smartreward corruption, too long to rebuild -- sugestion of solution

Smartrewards is a unique feature from Smartcash, and shall be treated in with the very same importance of the wallet.dat of bitcoin.

Thus, I would like to suggest the creation of a checkpoint.
Every n blocks, the daemon will create a copy of the smartrewards database.
If an expected and improper shutdown happen (ie. the usage suggestion includes a dedicated and non trustworthy VPS) the systemd may restart and the daemon can resume the smartrewards from the checkpoint, instead starting from ground zero

Wallet 2.0.2 Stuck connecting to peers

Hi Guys,

I've updated to OSX wallet 2.0.2 but it still says connecting to peers. I've tried deleting peers.dat and rerunning but no luck.

Any suggestions as to what to do next?

Also my linux node says:-

./smartcash-cli smartnode status
{
  "outpoint": "COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295)",
  "service": "[::]:0",
  "status": "Node just started, not yet activated"
}

Tried this command:-
./smartcash-cli reconsiderblock $(./smartcash-cli getblockhash 2025813)

but getting:-

error code: -8
error message:
Block height out of range
error code: -1
error message:
reconsiderblock "hash"

Removes invalidity status of a block and its descendants, reconsider them for activation.
This can be used to undo the effects of invalidateblock.

smartnode status gives back error -32603

-->
error code: -32603
error message:
This is not a smartnode

Why is that ? I installed the coresmart wallet, last version to set up my MN manually
Thanks a lot

Questions about upgrading from 1.2.8 to 1.3.0

Regarding the 1.3.0 version upgrade, I have the following three questions

1. Is there any change in the rpc interface, if so, what are the specific details of the change?
2. Can you explain the time lock?
3. Among the transaction data obtained through the rpc interface, from which items can it be determined that the transaction is time-locked?
4. Can the address in the legacy format continue to be used?

thank you very much

build fails with --disable-wallet configure switch

Attempting to make with the --disable-wallet option, yields errors.