BiblePay - New Coin Launch - Official Thread

[Shoko943]

I've been debugging this issue this morning, and have come to the conclusion we need to take one step back.  We took two steps forward with F7000, but I think we bit a little too much off at once.

The issue is in the biblehash suffix, in the txid portion in some cases it is not deterministic.

So what I would like to do is fix the problem, send out a mandatory and halt the exchange.

I instructed c-cex to go ahead and put us in maintenance.

Im compiling a mandatory upgrade, 1.0.3.1 now.  For all you linux folks, go ahead and grab it now, and let us pre-test it in prod.
(I just tested in Testnet, and its passing, but my network is too small to ensure this will be 'the final working' version).

Windows is compiling now.

The plan is we go with 1031, re-enable exchanges, burn this in, start a slack team, and then debug the txid suffix issue in testnet.

So basically, we still go live with F7000 - which eliminates X11, but without the txid lookback suffix.  We will debug that suffix in testnet with the new IT team.

How does that new mandatory work? Does it get activated after a certain block height? I just upgraded to 1.0.3.1 but I'm not sure if I'm on the right chain or not.

[svirusxxx2]

I'am too not sure
now I have my 10 computers upgraded to new version and one server.
my main node is open

Code:

addnode "vrs2.hostv.pl" "onetry"

I can't connect to node.biblepay.org :/

[inblue]

Meanwhile, pool gave everyone 0 credit for block 7143.

[tiras]

@tiras: You are ahead of time, check your latest block. I am on 7165 now, so different fork lol. Also, I think those machines you upgraded are now not hitting the pool anymore, check it. My 1.0.3.1 instances are not hitting the pool, and 1.0.2.9 are.

@inblue  ,  yes,  my both upgraded servers are not hitting the pool too atm    and   there was no credit @ 1:53:01 PM   :



MINING_CREDIT   7220f5c6-c983-4d70-a4ba-42279bf3fd8d   0.0000   33028.5011   9/11/2017 1:53:01 PM   7143

[bible_pay]

All,

The windows version of 1.0.3.1 has just been released.

(Someone asked about the cutover height.  I left the height as-is at 7000 while we check to see if our checkblock errors are alleviated).  If this fixes the problem, the chain will roll back to the highest block with the most work that satisfies the bible hash after 7000. 

Please upgrade from :
www.biblepay.org

[bible_pay]

@tiras: You are ahead of time, check your latest block. I am on 7165 now, so different fork lol. Also, I think those machines you upgraded are now not hitting the pool anymore, check it. My 1.0.3.1 instances are not hitting the pool, and 1.0.2.9 are.

@inblue  ,  yes,  my both upgraded servers are not hitting the pool too atm    and   there was no credit @ 1:53:01 PM   :



MINING_CREDIT   7220f5c6-c983-4d70-a4ba-42279bf3fd8d   0.0000   33028.5011   9/11/2017 1:53:01 PM   7143

I will check everything after 7000 in a bit after we see where the chain rolls back to when we get our supermajority on 1.0.3.1.  After that I will delete the bad blocks and let the pool re-pay.

[oliwer21]

I made payout form pool and coins dont come to wallet...

[PhaseshiftUK]

All,

The windows version of 1.0.3.1 has just been released.

(Someone asked about the cutover height.  I left the height as-is at 7000 while we check to see if our checkblock errors are alleviated).  If this fixes the problem, the chain will roll back to the highest block with the most work that satisfies the bible hash after 7000.  

Please upgrade from :
www.biblepay.org

I've compiled this on Linux, but it crashes on daemon startup:

$ ../start-biblepay.sh
Biblepay Core server starting
block.nTime = 1496347844
block.nNonce = 12
block.GetHash = 3b4431310395638c0ed65b40ede4b110d8da70fcc0c2ed4a729fb8e4d78b4452
block.hashMerkleRoot = 02b05f3b8a7168bcf83b888e0092446b248b2641bd9844b5d12a45eaa2765725
BlockMerkleRoot(block) = 02b05f3b8a7168bcf83b888e0092446b248b2641bd9844b5d12a45eaa2765725
block hash target = 3b4431310395638c0ed65b40ede4b110d8da70fcc0c2ed4a729fb8e4d78b4452

Error: Error: A fatal internal error occurred, see debug.log for details
biblterminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc


The relevant part of debug.log:

...
2017-09-11 20:34:15 89UpdateTip: new best=3a5700039aae2e1c6837d958cd98904509ecb7555d4d7d5a0b8dbf47ddbc0f50  height=7154  log2_work=35.706699  tx=10956  date=2017-09-11 20:27:28 progress=0.999957  cache=0.0MiB(73tx)
2017-09-11 20:34:15 ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level with TxIndex Lookup, prevheight 7118.000000 pindexPrev 268cc86887fb68f0081499cdc149b648239de01d625715313e7e1a8519bb6af4
2017-09-11 20:34:16 ERROR: CheckBlockHeader(): proof of work failed
2017-09-11 20:34:16 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-11 20:34:16 Misbehaving: 94.130.53.103:40000 (0 -> 50)
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
...
2017-09-11 20:34:16 UpdateTip: new best=edb60b03abf82be4b61a0e2b01da031076aa687a4385ac9cdf42bed296212bbc  height=7132  log2_work=35.669003  tx=10917  date=2017-09-11 16:24:31 progress=0.998414  cache=0.0MiB(34tx)
2017-09-11 20:34:16 ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7131.000000 pindexPrev b3afeb899bbb5ec99048e8f11c8f289ee93c44c3ecbdbb7378b537ba189c3b92
2017-09-11 20:34:16 ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=3111451)*** Failed to read block
2017-09-11 20:34:16 Error: Error: A fatal internal error occurred, see debug.log for details
2017-09-11 20:34:16 ERROR: ProcessNewBlock: ActivateBestChain failed
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:16 89ERROR: CheckProofOfWork(): BibleHash does not meet POW level, prevheight 7140.000000 pindexPrev ee4c915513dbf7e63f6f1134e4cb7df1a0b015f4c45165d7a7b85996cdf7462f
2017-09-11 20:34:16 ERROR: CheckBlockHeader(): proof of work failed
2017-09-11 20:34:16 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-09-11 20:34:16 Misbehaving: 94.130.53.103:40000 (50 -> 100) BAN THRESHOLD EXCEEDED
2017-09-11 20:34:16 CBlock(hash=474a203b6a6b890c9386030603b9220fa67325a0657916555b8ac20204cc47ac, ver=536870913, hashPrevBlock=3a5700039aae2e1c6837d958cd98904509ecb7555d4d7d5a0b8dbf47ddbc0f50, hashMerkleRoot=edbb579e581c86fe1c3fe55b3f69c51e0c293bd8c31885f973b1913f6e65e646, nTime=1505162056, nBits=1d69db8f, nNonce=1240, vtx=1)
  CTransaction(hash=edbb579e58, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02f31b0102)
    CTxOut(nValue=20000.00000000, scriptPubKey=76a914191de17e6075b5ef315978fb)


2017-09-11 20:34:16 generated 20000.00
2017-09-11 20:34:16 ERROR: ProcessBlockFound -- generated block is stale
2017-09-11 20:34:16 CBlock(hash=474a203b6a6b890c9386030603b9220fa67325a0657916555b8ac20204cc47ac, ver=536870913, hashPrevBlock=3a5700039aae2e1c6837d958cd98904509ecb7555d4d7d5a0b8dbf47ddbc0f50, hashMerkleRoot=edbb579e581c86fe1c3fe55b3f69c51e0c293bd8c31885f973b1913f6e65e646, nTime=1505162056, nBits=1d69db8f, nNonce=1240, vtx=1)
  CTransaction(hash=edbb579e58, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02f31b0102)
    CTxOut(nValue=20000.00000000, scriptPubKey=76a914191de17e6075b5ef315978fb)


2017-09-11 20:34:16 generated 20000.00
2017-09-11 20:34:16 ERROR: ProcessBlockFound -- generated block is stale
2017-09-11 20:34:16 tor: Thread interrupt
2017-09-11 20:34:16 torcontrol thread exit
2017-09-11 20:34:16 mnbcon thread interrupt
2017-09-11 20:34:16 dnsseed thread interrupt
2017-09-11 20:34:16 msghand thread interrupt
2017-09-11 20:34:16 scheduler thread interrupt
2017-09-11 20:34:16 opencon thread interrupt
2017-09-11 20:34:16 net thread interrupt
2017-09-11 20:34:17 CBlock(hash=1d63656d8de3271d18e0510f87fd9fa38ee5c92bfe94523979a1abaaa32c95bf, ver=536870913, hashPrevBlock=edb60b03abf82be4b61a0e2b01da031076aa687a4385ac9cdf42bed296212bbc, hashMerkleRoot=215c248ac9be7846abc1baed91a1d5c90d8f2d6f5ad57ff2d6fae970ac40c322, nTime=1505162056, nBits=1d189272, nNonce=7837, vtx=2)
  CTransaction(hash=531f8461aa, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02dd1b0101)
    CTxOut(nValue=19999.00004580, scriptPubKey=76a914191de17e6075b5ef315978fb)

  CTransaction(hash=4e89c8f7a2, ver=1, vin.size=1, vout.size=2, nLockTime=7101)
    CTxIn(COutPoint(dc3b3d2da31fa5bbf81f64692d0bd8fc088543b2c91382ae10c27190ebe8453d, 0), scriptSig=483045022100b07dd0aeac10, nSequence=4294967294)
    CTxOut(nValue=9045.00020980, scriptPubKey=76a9149d1839c28d967bb1d143276c)
    CTxOut(nValue=10831.00000000, scriptPubKey=76a914545914cda83830fbe39a83b6)


2017-09-11 20:34:17 generated 19999.0000458
2017-09-11 20:34:17 89ProcessNewBlock : ACCEPTED
...
2017-09-11 20:34:18 generated 19999.0000458
2017-09-11 20:34:18 89ProcessNewBlock : ACCEPTED
2017-09-11 20:34:18 addcon thread interrupt
2017-09-11 20:34:18 PrepareShutdown: In progress...
2017-09-11 20:34:18 StopNode()
2017-09-11 20:34:18 Verifying mncache.dat format...
2017-09-11 20:34:18 Loaded info from mncache.dat  0ms
2017-09-11 20:34:18      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-09-11 20:34:18 Writting info to mncache.dat...
2017-09-11 20:34:18 Written info to mncache.dat  0ms
2017-09-11 20:34:18      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-09-11 20:34:18 mncache.dat dump finished  0ms
2017-09-11 20:34:18 Verifying mnpayments.dat format...
2017-09-11 20:34:18 Loaded info from mnpayments.dat  0ms
2017-09-11 20:34:18      Votes: 0, Blocks: 0
2017-09-11 20:34:18 Writting info to mnpayments.dat...
2017-09-11 20:34:18 Written info to mnpayments.dat  0ms
2017-09-11 20:34:18      Votes: 0, Blocks: 0
2017-09-11 20:34:18 mnpayments.dat dump finished  0ms
2017-09-11 20:34:18 Verifying governance.dat format...
2017-09-11 20:34:18 Loaded info from governance.dat  0ms
2017-09-11 20:34:18      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-11 20:34:18 Writting info to governance.dat...
2017-09-11 20:34:18 Written info to governance.dat  0ms
2017-09-11 20:34:18      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-09-11 20:34:18 governance.dat dump finished  0ms
2017-09-11 20:34:18 Verifying netfulfilled.dat format...
2017-09-11 20:34:18 Loaded info from netfulfilled.dat  0ms
2017-09-11 20:34:18      Nodes with fulfilled requests: 0
2017-09-11 20:34:18 Writting info to netfulfilled.dat...
2017-09-11 20:34:18 Written info to netfulfilled.dat  1ms
2017-09-11 20:34:18      Nodes with fulfilled requests: 0
2017-09-11 20:34:18 netfulfilled.dat dump finished  1ms
2017-09-11 20:34:19 Shutdown: done

[maarekelets]

All,

The windows version of 1.0.3.1 has just been released.

(Someone asked about the cutover height.  I left the height as-is at 7000 while we check to see if our checkblock errors are alleviated).  If this fixes the problem, the chain will roll back to the highest block with the most work that satisfies the bible hash after 7000. 

Please upgrade from :
www.biblepay.org

I just went to the site to upgrade my windows machine, and the exe it downloaded says that it is still 1.0.2.9 in the details of it as well as when it installs. Is there a direct DL link to the 1.0.3.1 windows client?

I'm assuming for my linux clients I can just rebuild with code from github after I pull from it.

[svirusxxx2]

I will check everything after 7000 in a bit after we see where the chain rolls back to when we get our supermajority on 1.0.3.1.  After that I will delete the bad blocks and let the pool re-pay.

ok... my miners mining on wrong chain ... what is good chain, some peers/nodes or something ?

[tiras]

@tiras: You are ahead of time, check your latest block. I am on 7165 now, so different fork lol. Also, I think those machines you upgraded are now not hitting the pool anymore, check it. My 1.0.3.1 instances are not hitting the pool, and 1.0.2.9 are.

@inblue  ,  yes,  my both upgraded servers are not hitting the pool too atm    and   there was no credit @ 1:53:01 PM   :



MINING_CREDIT   7220f5c6-c983-4d70-a4ba-42279bf3fd8d   0.0000   33028.5011   9/11/2017 1:53:01 PM   7143

I will check everything after 7000 in a bit after we see where the chain rolls back to when we get our supermajority on 1.0.3.1.  After that I will delete the bad blocks and let the pool re-pay.

thanks ,

1.0.3.1 is working now :

Code:

/biblepay-cli getmininginfo
{
  "blocks": 7175,
  "currentblocksize": 1227,
  "currentblocktx": 1,
  "difficulty": 5.838335793673828,
  "errors": "",
  "genproclimit": 16,
  "networkhashps": 912444859.5115511,
  "hashps": 30325.51554411665,
  "minerstarttime": "09-11-2017 20:33:17",
  "pooledtx": 1,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVj
WVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtr
HSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSEL
MS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; 
B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jtJfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; B6jt
JfhZzbqiNUXfoQ2LdHVjWVtrHSELMS; ",
  "poolinfo2": "Submitting Solution 09-11-2017 20:57:51; RM_09-11-2017 20:57:57; Submitting Solution 09-11-2017 
20:57:31; Submitting Solution 09-11-2017 20:57:58; RMC_09-11-2017 20:57:46; RMC_09-11-2017 20:57:23; Submitting 
Solution 09-11-2017 20:57:35; Submitting Solution 09-11-2017 20:57:51; RM_09-11-2017 20:57:32; RM_09-11-2017 20:
57:41; RMC_09-11-2017 20:57:50; Submitting Solution 09-11-2017 20:57:59; RMC_09-11-2017 20:57:33; RMC_09-11-2017
 20:57:44; RMC_09-11-2017 20:57:47; RMC_09-11-2017 20:57:57; ",
  "poolinfo3": "INVALID_SOLUTION; INVALID_SOLUTION; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_DOWN; HEALTH_D
OWN; HEALTH_DOWN; INVALID_SOLUTION; ",
  "miningpulse": 1370,
  "poolmining": true
}

[haladez]

Is the pool on the main chain?
I think I got the issue resolved since my test withdraw appeared on my wallet.

Looks like the difficulty spiked to 10

---

Block explorer seems to be on a different chain.
http://biblepay.inspect.network/

[oliwer21]

Ok, next test Withdraw didn't come?
Whats going on? does anyone have the same problem?

[bible_pay]

Ok, next test Withdraw didn't come?
Whats going on? does anyone have the same problem?

Dont try to withdraw on a fork, lets upgrade to 1031 and ensure 'run versionreport' shows a supermajority.

[oliwer21]

Ok, next test Withdraw didn't come?
Whats going on? does anyone have the same problem?

Dont try to withdraw on a fork, lets upgrade to 1031 and ensure 'run versionreport' shows a supermajority.

Ok, so what with my coins?

[inblue]

Pool is now on height 4714.

[emdes]

What a mess  

EDIT: 0 active connections on 5 miners. Next wallet please  

EDIT2: Working now. Had to wait 15 minutes.

[Iwuzhaxxed]

Oh Shit! I made a withdrawl from the pool before checking this thread! dammit I hope my coins are okay. They haven't arrived in any of my wallets but I can confirm that we are now on multiple forks. The latest version of the client didn't help resolve the problem either..

[ylpkm]

Oh Shit! I made a withdrawl from the pool before checking this thread! dammit I hope my coins are okay. They haven't arrived in any of my wallets but I can confirm that we are now on multiple forks. The latest version of the client didn't help resolve the problem either..

Same here.

[jamie1989]

1st time posting, i been mining this for around 5hours got just over 1k coins, but is still immature balance, how long does it take till its available so i can withdraw ?