EXCHANGES that have responded as being updated to v2.1.3.0
NovaExchange
Bittrex
Topic: [ANN][PIVX] - PRIVATE INSTANT VERIFIED TRANSACTION - PROOF OF STAKE - ZEROCOIN - page 313. (Read 782375 times)
September 28, 2016, 12:26:01 PM
September 28, 2016, 12:08:47 PM
ok, false alarm.. updating masternodes with version
darknet-cli getinfo
{
"version" : 2010300,
"protocolversion" : 70705,
"walletversion" : 61000,
...
...
...
}
**** failure on masternode (:
2016-09-28 16:45:44 getblocks 317433 to end limit 500 from peer=37
2016-09-28 16:45:44 ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*) : GetHash() doesn't match index
darknet-cli getinfo
{
"version" : 2010300,
"protocolversion" : 70705,
"walletversion" : 61000,
...
...
...
}
**** failure on masternode (:
2016-09-28 16:45:44 getblocks 317433 to end limit 500 from peer=37
2016-09-28 16:45:44 ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*) : GetHash() doesn't match index
Re-Sync the chain from scratch
September 28, 2016, 11:41:02 AM
ok, false alarm.. updating masternodes with version
darknet-cli getinfo
{
"version" : 2010300,
"protocolversion" : 70705,
"walletversion" : 61000,
...
...
...
}
**** failure on masternode (:
2016-09-28 16:45:44 getblocks 317433 to end limit 500 from peer=37
2016-09-28 16:45:44 ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*) : GetHash() doesn't match index
resynced again up to "blocks" : 317560 , master up... upgrading rest ...
darknet-cli getinfo
{
"version" : 2010300,
"protocolversion" : 70705,
"walletversion" : 61000,
...
...
...
}
**** failure on masternode (:
2016-09-28 16:45:44 getblocks 317433 to end limit 500 from peer=37
2016-09-28 16:45:44 ERROR: ReadBlockFromDisk(CBlock&, CBlockIndex*) : GetHash() doesn't match index
resynced again up to "blocks" : 317560 , master up... upgrading rest ...
September 28, 2016, 11:16:33 AM
I cant get masternode started with new version 2.1.3
Windows standalone MN on Windows 7 64bit.
"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.
Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"
Didnt have this issue with the previos upgrades
Windows standalone MN on Windows 7 64bit.
"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.
Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"
Didnt have this issue with the previos upgrades
same message for me, we are still on testnet yeah ? probably why message above, putting testnet=true in config.. verifying if this is why
putting testnet=1 in the config results..
Error: Invalid masternodeprivkey. Please see documenation.
devs.. we are both receiving "Could not connect" with 2.1.3 .. we should hold off master nodes deployment ? thanks!
September 28, 2016, 10:59:51 AM
I cant get masternode started with new version 2.1.3
Windows standalone MN on Windows 7 64bit.
"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.
Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"
Didnt have this issue with the previos upgrades
Windows standalone MN on Windows 7 64bit.
"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.
Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"
Didnt have this issue with the previos upgrades
same message for me, we are still on testnet yeah ? probably why message above, putting testnet=true in config.. verifying if this is why
putting testnet=1 in the config results..
Error: Invalid masternodeprivkey. Please see documenation.
devs.. we are both receiving "Could not connect" with 2.1.3 .. we should hold off master nodes deployment ? thanks!
September 28, 2016, 09:13:37 AM
I cant get masternode started with new version 2.1.3
Windows standalone MN on Windows 7 64bit.
"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.
Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"
Didnt have this issue with the previos upgrades
Windows standalone MN on Windows 7 64bit.
"Not capable masternode: Could not connect to xx.xx.xxx.xx:51472"
Fully connected with other peers both In and Out.
Switching back to version 2.1.2.3 and masternode starts without issue:
"Masternode successfully started"
Didnt have this issue with the previos upgrades
September 28, 2016, 08:49:45 AM
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this
i consider
You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet
Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy.
as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real)
Yeah, so it is really that simple. Open a terminal, cd to the directory where your binary is and enter "darknet-qt --testnet". It will automatically create a subdirectory in your data directory for the testnet stuffs. You will need some addnodes in the darknet.conf, the testnet and mainnet share the same darknet.conf. The 2 wallets will have no problems running at the same time as they use different ports.
Right now these are the current addnodes for testnet:
addnode=173.245.158.8:51474
addnode=68.108.10.35:51474
addnode=2qvm3datgwvjz2h5.onion:51474
addnode=5jdzosvcuxj6yfgc.onion:51474
addnode=pzgvmwwve2l7763v.onion:51474
Yes, we have some tor testnet wallets running already, more on tor than clearnet.
As more folks start running testnet wallets please share the ips and we will keep an updated list. I will add some hardcoded nodes to testnet in a future release.
ok
Test Wallet up and running
(so proud of myself)
- Syncing Sporks - super slow 1/5 in and seems stuck
"please share the ips"
what is ips ?
get me some tcoins please
yD4ncrGqBxMXSbGzEkThp6rb7ZYfuPwJnv
is there a testgroup or something ? or you give further instructions here ?
Join the slack darknet-crypto.slack.com
September 28, 2016, 07:44:06 AM
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this
i consider
You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet
Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy.
as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real)
Yeah, so it is really that simple. Open a terminal, cd to the directory where your binary is and enter "darknet-qt --testnet". It will automatically create a subdirectory in your data directory for the testnet stuffs. You will need some addnodes in the darknet.conf, the testnet and mainnet share the same darknet.conf. The 2 wallets will have no problems running at the same time as they use different ports.
Right now these are the current addnodes for testnet:
addnode=173.245.158.8:51474
addnode=68.108.10.35:51474
addnode=2qvm3datgwvjz2h5.onion:51474
addnode=5jdzosvcuxj6yfgc.onion:51474
addnode=pzgvmwwve2l7763v.onion:51474
Yes, we have some tor testnet wallets running already, more on tor than clearnet.
As more folks start running testnet wallets please share the ips and we will keep an updated list. I will add some hardcoded nodes to testnet in a future release.
ok
Test Wallet up and running
(so proud of myself)
- Syncing Sporks -
"please share the ips"
what is ips ?
get me some tcoins please
yD4ncrGqBxMXSbGzEkThp6rb7ZYfuPwJnv
is there a testgroup or something ? or you give further instructions here ?
September 28, 2016, 07:03:00 AM
Have updated some of my masternodes today to v2.1.3.0. Zero issues. Will try to do the rest before the weekend.
September 28, 2016, 05:51:57 AM
Ok testnet wallet running here. Can I please have some tdnet love here? yBh7yX6ifGWLiobLiug7J9HiJXXpMgHsTH
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
I'll send a bit.
Don't spend it all in one place.
Got 50k now. Thanks!
September 28, 2016, 05:21:31 AM
Ok testnet wallet running here. Can I please have some tdnet love here? yBh7yX6ifGWLiobLiug7J9HiJXXpMgHsTH
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
I'll send a bit.
Don't spend it all in one place.
September 28, 2016, 03:47:16 AM
Ok testnet wallet running here. Can I please have some tdnet love here? yBh7yX6ifGWLiobLiug7J9HiJXXpMgHsTH
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
Would you like me to start mixing or just staking?
edit: I get stucked at 25% spork sync and 1 connection to the network.
September 28, 2016, 03:18:07 AM
all wallets and MN's updated
will look into that testnet wallet later on
(tx for the details)
will look into that testnet wallet later on
(tx for the details)
September 28, 2016, 02:57:22 AM
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this
i consider
You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet
Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy.
as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real)
Yeah, so it is really that simple. Open a terminal, cd to the directory where your binary is and enter "darknet-qt --testnet". It will automatically create a subdirectory in your data directory for the testnet stuffs. You will need some addnodes in the darknet.conf, the testnet and mainnet share the same darknet.conf. The 2 wallets will have no problems running at the same time as they use different ports.
Right now these are the current addnodes for testnet:
addnode=173.245.158.8:51474
addnode=68.108.10.35:51474
addnode=2qvm3datgwvjz2h5.onion:51474
addnode=5jdzosvcuxj6yfgc.onion:51474
addnode=pzgvmwwve2l7763v.onion:51474
Yes, we have some tor testnet wallets running already, more on tor than clearnet.
As more folks start running testnet wallets please share the ips and we will keep an updated list. I will add some hardcoded nodes to testnet in a future release.
so the recent version is 2.1.3?
the payment information page shows: client version: 2010204, this is a bit confusing!
should we remove the 3 lines (nodes, bantime) from conf file with this update?
I'm trying to run a wallet on testnet on my staking pc. added the lines above to my darknet.conf and starting the wallet with "darknet-qt --testnet"
the wallet is stuck at "synchronizing sporks, synchronizing additional data 25%"
waiting for hrs now still at 25%, and only have 1 connection on testnet wallet, restart the testnet wallet does not help, any ideas?
September 28, 2016, 02:36:18 AM
EXCHANGES that have responded as being updated to v2.1.3.0
NovaExchange
NovaExchange
What about trex? will wallet work?
September 27, 2016, 11:54:47 PM
Sorry for the question, but I have a rapsberry pi that could run a testnet wallet 24 hours per day, but I always use windows wallets, so not very familiar about how to run a testnode. Any manual, tutorial or similar out there?
Salute
Salute
September 27, 2016, 10:48:08 PM
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this
i consider
You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet
Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy.
as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real)
Yeah, so it is really that simple. Open a terminal, cd to the directory where your binary is and enter "darknet-qt --testnet". It will automatically create a subdirectory in your data directory for the testnet stuffs. You will need some addnodes in the darknet.conf, the testnet and mainnet share the same darknet.conf. The 2 wallets will have no problems running at the same time as they use different ports.
Right now these are the current addnodes for testnet:
addnode=173.245.158.8:51474
addnode=68.108.10.35:51474
addnode=2qvm3datgwvjz2h5.onion:51474
addnode=5jdzosvcuxj6yfgc.onion:51474
addnode=pzgvmwwve2l7763v.onion:51474
Yes, we have some tor testnet wallets running already, more on tor than clearnet.
As more folks start running testnet wallets please share the ips and we will keep an updated list. I will add some hardcoded nodes to testnet in a future release.
September 27, 2016, 10:09:48 PM
Add testnet=1 in your darknet.conf file, the change the addnodes.
you can also cd from a terminal to the binary location of the wallet, and run './darknet-qt -testnet' Which will start the wallet in testnet mode.
Personally, I run mine in VM's so each wallet has it's own environment. All will work just fine
you can also cd from a terminal to the binary location of the wallet, and run './darknet-qt -testnet' Which will start the wallet in testnet mode.
Personally, I run mine in VM's so each wallet has it's own environment. All will work just fine
September 27, 2016, 10:06:09 PM
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this
i consider
You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet
Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy.
tx for the "yell" at s3v3n
as well how do i run 2nd wallet on 1 computer (1 testnet - 1 real)
September 27, 2016, 09:59:47 PM
OK folks, we have a working testnet finally, That will allow us to more thoroughly test updates ahead of time, but we will need the help of the community. If you are able to fire up a wallet on testnet get addresses to us and we will throw some coins your way. We need stakers, masternodes, people mixing, etc. to fully test things.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
You can run the testnet along side your primary wallet, they will not conflict with each other. There is no need to specify a data directory, it will create a subfolder in the default data directory and the chain, wallet, etc. will be there. The only shared file will be the darknet.conf.
if you have an (idiot proved) mac guide for this
i consider
You just start the wallet with the --testnet flag. So, for the qt, ./darknet-qt --testnet
Edit: There may be a slightly different syntax for starting programs on Mac than Linux, let me yell to s3v3n, he is the Mac guy.
Jump to: