Search results

12.1 has two option on InstantSend notify 1) dashd cmd option -instantsendnotify=<cmd> Execute command when a wallet InstantSend transaction is successfully locked (%s in cmd is replaced by TxID) 2) dashd zmq option -zmqpubhashtxlock=<address> Enable publish hash...

masternode start using keepkey + dashd https://github.com/chaeplin/dash-testnet/tree/master/keepkey_mnb

There was an update on sentinel on block 124630 ~ 124650.

I have setup a service for InstantSend https://test.stats.dash.org/is/ Send X tDash to address in page using InstantSend, will get Y tDash using InstantSend. (Normal tx will get Y tDash after 6 confirmation) if received tDash <= 1 --> send 1 if received tDash > 10 --> send 5 (thank you) if...

Known Problem.

nomp and http://tdrk.poolhash.org/ updated.

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html found this. http://engineering.silk.co/post/31923247961/multiple-ip-addresses-on-amazon-ec2 http://work.allaboutken.com/node/21

Use 1 interface. With 2 interface, I think you have to use iproute2 utility. iproute2 is more complicated, so one interface is best practice. If you can get more EIP, add more private in EC2 console. At instance creation, add more private At running instance, using 'Network Interfces' menu...

Send 1K to own address(holding 1K) again using cold wallet. It will invalidate previous entry. After 7 confirmation, start Masternode. Usually 'masternode stop' will remove duplicated entry. But if you have problem, send 1K to a new address or own address. I use 'own address', because I don't...

Changed to 140458

* Updating Masternode * 1) stop darkcoind (locl and remote) 2) Update darkcoind(locl and remote) 3) remove peers.dat(locl and remote) 4) Start darkcoind(locl and remote) Check drkcoind status using 'darkcoind getinfo' and 'darkcoind masternode current' Compare block no and current masternode...

Just stop darkcoind, update darkcoind(remote and local). start it. Using local wallet(updated), start masternode. No need to update ip or key.

eduffield flare Looks like "enforce_masternode_payments" is gone in getblocktemplate of 101314 user@sv3:~> darkcoind getinfo { "version" : 101314, "protocolversion" : 70038, ~~~ "height" : 140427, "votes" : [ ], "payee" : "XsZCTymDd4dLWsBNwCSDJqXfdWz3KSejJ6"...

Did you restart masternode using cold wallet ?

I don't think secondary interface is good choice. Anyway you can use ifconfig to set up eth1. I suggest you to use "Network Interfaces" in EC2 Management Console to add more private IPs. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html There is "Manage Private IP Address" in...

There is a request form for elastic ips.

eduffield I have a question on enforcement. After restarting Darkcoind, payee of getblocktemplate is empty for some period. What happens when a pool(on a newly restarted Darkcoind) found a block in this status ? darktest@sv1:~> darkcoind getblocktemplate { "version" : 2...

I have found a option '-disablesafemode'. I have relaunched a node with the option.

Solved with option "disablesafemode" I have this error "errors" : "Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade." and this darktest@sv1:~> darkcoind masternode list error: {"code":-2,"message":"Safe mode: Warning: Displayed...

https://github.com/darkcoinproject/darkcoin/commit/430a9f17a83caa373eb235caaabb722ec7d6bede protocol version is not updated.