Messages

1846

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 11, 2019, 04:23:20 PM »

I will reach you tomorrow so we can do some tests with private send on testnet.

Thanks, this will help sooo much.

1847

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 10, 2019, 12:47:32 PM »

CPID                                                                TEAM
168c62b82fb40fa3db0d34605439daa5    Biblepay
25a7e68bd686ffe82e00330f1390e003     Gridcoin
5f4e0dea9b0ddf2471cac1e9244a7026     Gridcoin

Ok everything looks good; so right now, the only team name being displayed in the wallet in exec rac is "BiblePay".  So on your two GRC cpids, we don't yet show the TeamName.  However I whitelisted (that team) so in about 24 hours you should see the teamname show up (but note this doesn't affect anything in the whole system - including payments).

So people in an unknown team still get paid, and charged the correct escrow reqs.

1848

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 10, 2019, 10:52:43 AM »

Linux x64 testnet

>cli -version
BiblePay Core RPC client version 1.4.8.4

>cli getblockcount
21050
>cli getblockhash 21050
c050dc13103b96de932787ed502520654ea13ba013528ba10b39a97a63f67681

Mine does not agree with yours (I get e36 for that hash).

Ill resync a node and see what chain jumped; hang on.  This happens every mandatory upgrade due to private quorums, I believe.

EDIT: Ok, you guys apparently bounced the chain with much more hashpower than my piddly sancs had, so I had to resync my 4 nodes but now I agree with oncoas hash on 21050.

So, I just sent the revivesanc command to my 3 sancs, lets see if we unban ourselves now.

1849

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 10, 2019, 10:49:41 AM »

Output of exec rac

Code: [Select]

{
  "Command": "rac",
  "cpid": "xx003",
  "CPK": "xxb3d",
  "next_podc_gsc_transmission": 21217,
  "team_name": "Unknown",
  "external_purse_total_coin_age": 17926854.70136574,
  "coin_age_percent_required": 0.02855726425848298,
  "coin_age_required": 332673.380016672,
  "wcg_id": xxx83,
  "rac": 2826.58
}
{
  "Command": "rac",
  "cpid": "xxxaa5",
  "CPK": "xxxWPv",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 21217,
  "team_name": "Biblepay",
  "researcher_nickname": "oncoapop",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4548281.74,
  "total_wcg_points": 31837972.18,
  "external_purse_total_coin_age": 20668208.12225695,
  "coin_age_percent_required": 0.0170824277899341,
  "coin_age_required": 146381.0915732143,
  "wcg_id": xxx773,
  "rac": 9406.974910000001
}

Team          Ratio
Gridcoin    117.69
Biblepay      15.56

Team info for team Gridcoin (and perhaps other team than Biblepay) not working.

Thanks on the multiplier.  On the team info name:

I actually had to take out the team name in this version for all teams except BiblePay due to size constraints, since we are now going to support 27,000 new possible researchers, adding things like their nickname and team name and start date and total points just bloated the vectors to a degree that slowed down biblepay, so I took this stance:  We provide all the info for BiblePay, but for other teams, we only know your CPID and your RAC (and things about your rac metrics).  Then each month, the wallet will start to whitelist popular non-bbp teams, as we do that, it will pick up your team name and nickname etc.  In the mean time we use your CPK nickname now (for non BBP CPIDs).

If you provide your CPID (which is public btw, you dont have to x it out necessarily), I can search the BOINC XML files and see that everything is working OK, but I believe it is.

1850

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 10, 2019, 10:44:53 AM »

I have tested 1.4.8.4 against mainnet and everything seems to sync properly (chain, sans, proposals, leaderboard...)

Good.  And I started running one in the background and Ill leave it up.  So far it appears the governance info will sync through the next contract @162790, but we should watch it.  Ive solo mined successfully.  I tested nomp with it a few weeks ago also.

How about syncing in testnet, is that working for everyone?  I didnt have a problem upgrading or a researcher problem either.

I do see we have 3 POSE banned sancs; will the sancs please upgrade?  This way chainlocks wont blow out in testnet.

1851

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 09, 2019, 02:58:06 PM »

When my wallet was stuck at loading PoDC researchers, I thought I had a corrupt blockchain so I did the --erasechain option.


1484 doesn't go past this screen for me.


I can't exit BiblePay-qt.exe unless I end the task manually from Task Manager.


1483 didn't have this problem... this is why I looked at the code and asked about it because the screen is stuck on Loading PoDC researchers...

So which platform are you running 1484 on?
MIP said he just finished the compile, so does this mean you self compiled QT on linux?

Unable to reproduce:  On all four of my 1484 nodes, the researchers load.

I just tested on windows also, 1484 loads researchers on windows.

1852

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 09, 2019, 09:56:57 AM »

Is there a default value for the spork when start the blockchain from scratch?

https://github.com/biblepay/biblepay-evolution/commit/306653b982ee1907ac2b13e54030f131012aae2a#diff-a0c8f511d90e83aa9b5857e819ced344R3027

Yes, zero.

And the value is set to zero currently, so we are in "0" mode.

1853

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 09, 2019, 09:56:13 AM »

I'm stuck at Loading PoDC Researchers... for some reason.


Tried --erasechain and stuck there again.

What version are you running?

1854

Archived Proposals / Re: PODC TEAM REQUIREMENTS

« on: December 09, 2019, 09:54:41 AM »

I voted:
"Require nothing - give rewards to everyone"

But since no one else was voting for that I changed to:
"Require ^1.6 for non-bbp, ^1.3 for BBP (Allowing Any Team to be rewarded)"

2 days left guys.

1855

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 08, 2019, 06:01:27 PM »

BiblePay
1.4.8.4 - Mandatory Upgrade for TestNet

- Remove biblepaypool fields in getmininginfo
- Make PODC team configuration configurable by spork.  Allow any teams CPID to 'associate' or 'rac'.  Calculate the coin-age collateral req. exponent based on the config.
- Adjust DWS burn params for prod release.  Add DWS safety layer to double check rewards when the block exceeds the original base limit.  Require DWS rewards to be in the superblock if they exist.
- Enhance exec dwsquote 1 1 report to show a more consolidated report.
- Adjust Prod params to ready for mainnet release on Christmas

** All versions ready **

NOTE:  This version will also allow us to sync against mainnet, mine against mainnet, and verify the gsc passes in mainnet.  This version is theoretically the mainnet Christmas release candidate #1 (RC1).

1856

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 08, 2019, 04:59:13 PM »

Could someone please join that is outside GRC & BBP?

The next version should be ready in a few hours; we need to test a non-grc non-bbp cpid in podc2.0 to ensure the rewards come through.
Btw, your RAC has to be higher than 256 for this to work.

1857

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 08, 2019, 10:14:28 AM »

** TestNet Update **

- TestNet seems relatively stable.  I've burned about 50 DWS (and received them back) with 100% success.  I havent had any memory pool rejects in the latest version.  PODC appears to be working.  Unbanked appears to be working. 
- I see this poll: [https://forum.biblepay.org/index.php?topic=476.new;topicseen#new  ]  shows  a  potential interest in allowing all teams in, including GRC, with ^1.6.  I believe in light of this potential outcome, it would be prudent for us to create the code necessary for this, and have it ready within 2 days.  Ill be working on this later today, and making this into a spork for testnet.
- I have a minor change to check in for TestNets branch to run against prod; but Ill wait until I get the above release ready.  The current branch has been mining against prod, and keeping in sync with prod with the patch involved (but you do need the upcoming patch to run this branch against prod so please dont try it yet).

1858

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 06, 2019, 05:47:26 PM »

** HOST BRZ (www.hostbrz.com) UPDATE/GOING OUT OF BUSINESS **


Dear Customer,

Over the past few months we have been met with many challenges within the hosting business. Some that have not been overcome.
As result of this we will be closing our doors.  We will be shutting down this Monday 12/9/2019.  We are taking this time to let our customers know so that they may backup and retrieve all of their data before then.
We deeply apologize for this inconvenience.
Thank You.
 
Management

NOTE:  Hostbrz is only giving valuable customers 3 days to remove their data.  I believe they will be keeping the excess hosting fees and not offering a refund.

1859

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 06, 2019, 08:18:24 AM »

Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00821000 tBBP
Net amount: -11 000.00821000 tBBP
Transaction ID: c76dc628ab85cd1eefea170d649bb92aabf085c2a12b84b9d34a25518e6ec05c
Output index: 1
Transaction total size: 821 bytes

Code: [Select]

Debit: -3767.05326650 tBBP
Debit: -3773.29547908 tBBP
Debit: -5065.13451406 tBBP
Credit: 1605.47504964 tBBP
To: yLdnz7dQxUZCpcX1Z9bcBbFz2QBRQgMGZn 1605.0000 BBP

Transaction:
CTransaction(hash=c76dc628ab, ver=1, type=0, vin.size=3, vout.size=2, nLockTime=20102, vExtraPayload.size=0)
    CTxIn(COutPoint(7a4804ef0b14b94c37ca5083dc1675ef3c0d11637282529850c50263e2bc8202, 0), scriptSig=483045022100bde976efea0e, nSequence=4294967294)
    CTxIn(COutPoint(bde5dba4fc908e2fe106e5e5040dc213fae425b243a617f0ef6c793c220a2ebc, 0), scriptSig=483045022100a770d7458985, nSequence=4294967294)
    CTxIn(COutPoint(c241737398b8becad573bb9887cc659f3705ec684c24ff134e30bba034ef2668, 10), scriptSig=483045022100ffea81996b77, nSequence=4294967294)
    CTxOut(nValue=1605.47504964, scriptPubKey=76a91403784bdd3a4cf73272b0bcf3)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)

DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294901.8160312-08-2019 07:04:5011000.00





Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00821000 tBBP
Net amount: -11 000.00821000 tBBP
Transaction ID: ab6b451724d48b7204ccd5eedad550c2548fac764450f840e8ad14ac28e96a85
Output index: 1
Transaction total size: 819 bytes


Debit: -3779.16221232 tBBP
Debit: -5707.10526530 tBBP
Debit: -3780.86439835 tBBP
Credit: 2267.12366597 tBBP
To: yQzXVa2uKZf1ZvhPnf2WEmPVh9Lx3Q8YYY 2267.0000 BBP

Transaction:
CTransaction(hash=ab6b451724, ver=1, type=0, vin.size=3, vout.size=2, nLockTime=20043, vExtraPayload.size=0)
    CTxIn(COutPoint(34a9e058211f4b6b722b4d26ed096b2dcdcff482f11a6d75b7f1ae0fa4ae5fed, 0), scriptSig=4730440220199ae942e147ad, nSequence=4294967294)
    CTxIn(COutPoint(5e0a114a3c01706e76f06f8fb80557323b0b8af25f519585d00ab40afaf954d1, 10), scriptSig=473044022034d0f8f879de64, nSequence=4294967294)
    CTxIn(COutPoint(cf7001bdf3774d64d01832f79df9914d24c641ca14fa7d7742c698941a49d6af, 0), scriptSig=483045022100f16448095e47, nSequence=4294967294)
    CTxOut(nValue=2267.12366597, scriptPubKey=76a91433449a3c30ed33871f3d12f2)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)

DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294911.8159312-08-2019 07:04:5111000.00





Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00593000 tBBP
Net amount: -11 000.00593000 tBBP
Transaction ID: 4787a76368dd0715c36c90d02c9f7a65149d63646ab69ffdaf0155cc6231cd88
Output index: 0
Transaction total size: 593 bytes



Debit: -503 588.99953448 tBBP
Credit: 492 588.99360448 tBBP
To: yP5GznAJMkYnxggE3BM74FMGrWm2ZFCJML 492588.0000 BBP

Transaction:
CTransaction(hash=4787a76368, ver=1, type=0, vin.size=1, vout.size=2, nLockTime=20045, vExtraPayload.size=0)
    CTxIn(COutPoint(0b62094692049e33fcf3bc7eccb48ee02ae0cb3b9d087ac68cbc3d71b8a95203, 1), scriptSig=483045022100de2345fa4db9, nSequence=4294967294)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)
    CTxOut(nValue=492588.99360448, scriptPubKey=76a9141e3a5469ec7d6141cdf494dd)
DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294911.8158312-08-2019 07:04:5111000.00

Please encapsulate long 'pastes' within code tags.

Were you going to answer the other questions in my post?

Next, try to grep your own debug.log like this:
cd testnet3
cat debug.log | grep c76dc628ab85cd1eefea170d649bb92aabf085c2a12b84b9d34a25518e6ec05c

Please paste the error here.

Your burn is not on my sanctuary log, or in my dev node, so it did not make it onto the network.

1860

TestNet Discussion Archive / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: December 05, 2019, 09:12:26 AM »

Sorry, like I said, I removed the TX. If I run into again, I'll relay it.

How many did you successfully test before that?  Were you inserting a lot of DWS inside the same block, or trying to break it, or what lead up to the failed DWS transaction exactly?

Most likely you were able to get it transmitted locally because it passed all checks at that very second, but the other nodes on the network didnt like it (due to it being out of bounds by a certain parameter).  Once we have a future txid, I can tell you what the parameter was.

But after looking at the code, I dont see any flaws the way it is.  We do check the transaction before accepting it now, so it is not a matter of becoming an orphan because of the biblepay validator.