Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sdc

Pages: [1]
1
No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Got it. Thanks Rob!

2
Is the reduction in the superblock because of the tithe block?

3
Please ensure your 'exec getboincinfo' shows a valid CPID, then also that your wallet is unlocked and HPS > 0.

Yes to the above. I've been receiving regular rewards. What i meant was I downloaded 1.1.1.1 to test after reading warmoth's note. As soon as I noticed something odd with the behaviour, I immediately downgraded to 1.1.0.9b and it was fine. Was just wondering if there's a problem with 1.1.1.1 and perhaps podc updates?

4
I also tried 1.1.1.1 and it said unable to sign CPID when I was mining on Purepool.

5
OK. Just tested the send to myself and it seems to work as a PrivateSend Collateral Payment.
I think my mistake was that my wallet was locked.
I didn't realize that when you put in your password upon opening the Biblepay Core, that it didn't unlock the wallet. I had to click through Settings to unlock and then punch in the password again.
I just tried running another associate, but I'll have to wait for 5 blocks until the last DXBTX clears.

6
go into biblepaycore and look at the debug file, what does it say when you associate?

Is this the right section of the debug? I ran a search for associate and this is what I came up with.
Also, perhaps I missed a step? I followed Togo's guide for Windows. I set up a Rosetta@Home account and I can login with that email/password to their website.
The CPID below doesn't seem to match the one on my Rosetta account.

2018-03-07 21:33:28 GUI: QObject::connect: No such slot DistributedComputingDialog::clicked() in qt/distributedcomputingdialog.cpp:57
2018-03-07 21:33:28 GUI: QObject::connect:  (sender name:   'btnAssociate')
2018-03-07 21:33:28 GUI: QObject::connect:  (receiver name: 'DistributedComputingDialog')
2018-03-07 21:33:28 . model set .
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:35:56 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=144.202.64.156:40000
2018-03-07 21:36:01 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=104.238.158.39:40000
2018-03-07 21:38:09 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.216.160:40000
2018-03-07 21:38:24 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.218.12:40000
2018-03-07 21:38:37 CGovernanceManager::ProcessVote -- Unknown parent object , MN outpoint = f0db4fbdb37c627d55c83fb4bba953b0b01b80a996f86010d02a65a42a8192bc-1, governance object hash = 14ec3b00c46a8f1090be5bc46100e5df547f5e9ed6c3cba8a75ca72b4a9ef572
2018-03-07 21:39:34 RPC error
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- creating birth, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- update empty, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::ProcessTxLockRequest -- accepted, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000

7
RPC Error

Ah... then when I run it again it says.

 "Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

So basically, the first command produced an error, but running exec a second time assumes that the first command was successful. What is an RPC error anyways?

9
Wait 5 blocks, then close and restart your wallet. Run exec getboincinfo again and we'll go from there.

Done. Nothing 6 blocks later.


13:33:45

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


13:33:54

getblockcount


13:33:54

33447

10
Hey Mike, thanks for the quick response.

{
  "version": 1010003,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.3",
  "balance": 43.58675910,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33441,
  "timeoffset": 2,
  "connections": 8,
  "proxy": "",
  "difficulty": 1561.54112909823,
  "testnet": false,
  "keypoololdest": 1515744128,
  "keypoolsize": 1001,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

11
Hi guys

I'm trying to bring two machines on to the new PODC. Last night I tried the GUI to associate my Rosetta account with Biblepay. Waited and nothing showed up this morning. I ran it again earlier this morning and waited, still nothing. This is the current readout of getboincinfo from my debug. Am I right in understanding my CPID is NOT associated with my Biblepay wallet?

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422347,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

I just ran a command line associate a few blocks ago, and then I ran it again and it says.

"Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

I'm hoping this will work. But just wondering if anyone else had trouble with using the GUI to associate? Thanks.

Pages: [1]