Bible Pay

Recent Posts

Pages: 1 2 3 4 [5] 6 7 8 9 10
41
I saw in debug " 0 addresses found from DNS seeds" so I was planning in adding them manualy but ok.
 
prict from previus post
42
no, there is no reason. didnt even know I am hiding it.
I uncomment this below and now it got the connection.
#rpcuser=
#rpcpassword=
#rpcallowip=127.0.0.1
#rpcport=40001
#listen=0

Ok good, I was only asking because yesterday I saw some strange activity that looked like someone was sending things from a fraudulent client (IE a self compiled fraudulent client).

Yeah the addresses are:  dns1.biblepay.org, dns2.biblepay.org and dns3.biblepay.org

43
So I have a few pieces of advice for anyone creating new deterministic sancs:

1) Do not lose your masternodeblsprivkey (or pubkey).  Keep a copy of your deterministic.conf somewhere.  If you lose your wallet.dat, your sanc will keep running as long as the collateral is locked, and you will not be able to change its IP or its collateral without that blsprivkey and owner privkey.
2) However, I did a test today and found a way to immediately kill your old sanctuary (and allow upgrading).  If you spend your collateral, within minutes the sanctuary will dissapear from the active sancs list! 
3) You cannot re-register the same IP with a new sanc until you either Revoke your old sanctuary (with a proUpRevTx), or if you spend your collateral.

I was successfully able to re-create a new sanc today after I spent my collateral and did a new upgradesanc command.

If otoh you do an upgradesanc before spending and revoking, you will receive an error (duplicate service IP).

44
no, there is no reason. didnt even know I am hiding it.
I uncomment this below and now it got the connection.
#rpcuser=
#rpcpassword=
#rpcallowip=127.0.0.1
#rpcport=40001
#listen=0
45
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*

Synced

46
nope, something doesnt work at all. Like I am on my own


what are the nodes, i saw them in previus version, but cant remeber. ns.biblepay.org?
Like I alluded to in the prior message, they would be compiled in if they are seed nodes so you dont need them, and I synced today with a node.

Is there a reason you are hiding your ip?

47
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*

When you say crash, what do you mean, and what version are you running (qt or non) and what platform (unix linux mac)?

Yeah, since I have not seen a crash yet except clicking on leaderboard in prod (which was fixed in the last version) I would really like to know how to reproduce.

Also, if anyone else has ever crashed in evo in testnet it would be really nice to have more info so we can fix it before we go to prod (thats what testnet is for).

48
Upgraded both wallets to v1.4.2.8b yesterday

I tried to just run them normally, but they would crash right away, tried to reindex and same thing, didnt see anything in the log (may have forgotten to add debug=1), so I wanted till today and tried again with reindex, both worked a couple hours ago

getblockhash 69207
6e40d8f*
49
nope, something doesnt work at all. Like I am on my own


what are the nodes, i saw them in previus version, but cant remeber. ns.biblepay.org?
50
ha, to late. I deleted everything and now I have a problem, no peers

Check system clock ensure its correct within 5 mins and timezone is correct.

Delete banlist.dat, restart.

If you arent synced after 15 mins post IP address here and Ill search my log for the reason for your ban as we have 3 seed nodes in testnet.
Pages: 1 2 3 4 [5] 6 7 8 9 10