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 - Rob Andrews

Pages: 1 ... 130 131 132 133 134 135 136 [137] 138 139 140 141 142 143 144 ... 263
2041
I was able to download these two files using "wget URL" command:

Linux PC 64bits Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

But I had to remove the extra dash in evo--testnet for the daemon version

I was able to unzip with "tar xzvf FILE" command
I see biblepayd, biblepay-cli and biblepay-tx
Im running ./biblepayd with erasechain
and I ran getinfo and I see error message "Loading PODC Researchers..."

Now I have 3 connections and Im shooting up fast on blocks! Yay!

The "Loading PODC..." is the UI status message of where the daemon currently is in the load process.  Same as "Memorizing Prayers...".


2042
I assume since the privkey is public, anyone else could also claim those test coins,
Im trying to send them to a new address, but its saying "Signing transaction failed",
Maybe I have to wait a few confirmations?

Yes anyone can claim them til they are gone, or you can keep them and share them, either way.   If you only spend half then other people could take some but otoh it might be better if you are more available to resend them, either way works.


2043
I still seem to have troubles getting connections

My Test server IP address is:  155.138.220.139

My biblepay.conf file is:

Code: [Select]
testnet=1
addnode=testnet.biblepay.org
addnode=testnet1.biblepay.org
addnode=107.173.41.176:44610
addnode=107.173.41.176:39999
addnode=107.173.41.178:55584

Ive just been using daemon, havent setup/run the gui yet

getinfo shows my version as: 1040502

I have done -erasechain a couple times,
Ive even gone in a manually deleted almost everything in the /testnet3 folder

Maybe I just need to use a precompiled version?
I am now noticing that you have 1.4.6.7 in the posts,
whoops! on my end, Im on 1.4.5.2 from source
Ill use one of the precompiles and report back

Just to clarify this, especially for anyone trying to comprehend this, Note that any version within 1.4.5.0 - 1.4.5.9 is within the Prod (mainnet) branch - and we call this the 0.13 branch (it matches Dash's .13 branch).  This is the branch with hybrid sancs.  Note that that branch will not work in testnet at all; this is because in testnet - the .14 branch is 100% deterministic.

So for testnet, we must have the users run on 1.4.6.7 and up for these to sync.

Thats awesome you got the 1.4.6.7 up - and synced and match the hash.
I do recommend the GUI QT version for testing; as you can see a lot of these test cases are rather complicated.  They can probably be done within the daemon however.

So I do have a question though, we had a bug in 1.4.6.6 with the transaction signing.  MIP had reported that he deployed 1.4.6.7 where the fix is.  Could you please double check the reported version of your client?


2044
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks

Here is some free bbp for anyone who wants it :


16:51:54

dumpprivkey ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA


16:51:54

cUWA5YrRZteBEo1hnqWv3xquyDY4V9zyJTeSqHtFeiCmjJsTxVoT


To claim it, import the privkey with "importprivkey key".


2045
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks

Ive got to head out to a thing for my son, Togo do you have an address that needs tbbp, then you can give some to Capulo and MIP?

2046
BiblePay
1.4.6.7-Mandatory Upgrade for TestNet

- Fix 'fail to sign' transaction bug.

Hi Capulo, welcome aboard!

Binaries should be working and are in the OP post.


2047
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks

Ill check the dns records in a few mins, but in the mean time please try this:

addnode add 107.173.41.176:44610
addnode add 107.173.41.176:39999
addnode add 107.173.41.178:55584

Please try with onetry behind the command, also

EDIT:  I see our first dns record, testnet.biblepay.org is answering on 40001 please try that as addnode?  Ill have to check the code to see if that is still hardcoded in, but it appears to be working if you add it.

EDIT2:  Ok, I think our 2nd DNS server was pose banned, now I reinstated both testnet and testnet1 again, please try now.  (addnode testnet.biblepay.org, testnet1.biblepay.org)






2048
BiblePay
1.4.6.7-Mandatory Upgrade for TestNet

- Fix 'fail to sign' transaction bug.




2049

Ok, with PODC 2.0 coming soon, lets not use the Christian Spaces thread for testing.

Lets focus on:
-reviving our sanctuaries
-reviving our state in testnet
-ensuring we are synced
-enabling WCG miners so we can utilize the CPID and credit RAC in testnet

In the mean time, I will add a command to the develop branch that allows us to send the pro_reg Update Service command (the BiblePay way) - that takes advantage of the deterministic.conf file, so we can revive our failing sancs.

Please join us here and test PODC 2.0:


https://forum.biblepay.org/index.php?topic=465.msg6423#msg6423



2050
Test Cases:

1) Please ensure you have upgraded to 1.4.6.7+ (this was a mandatory upgrade).

2) Please ensure your sanctuary is not POSE banned.  If it is, you can easily unban it with this command:
exec revivesanc sanc_name

3) Please ensure you are synced on the correct chain in testnet.  The block # is about 14005:
getblockhash 14005       266323d2e7daa74d570577a667ad8ed536c622c1f0b286d39605a964eb5dce9a

4) Please ensure you have a CPK in testnet:  If you don't you can create one with:  exec cpk your_nickname

5) Start crunching WCG tasks, so that your RAC is building up.

6) Familiarize yourself with these commands:
https://wiki.biblepay.org/PODC

7) Ensure your external purse (Christian-Public-Key) is funded with enough TestNet collateral.  Please make a post here if you need tBBP.

8 ) Type 'exec rac' and verify no errors exist.

9) Verify the SendAllGSC's works from the main thread without the miner running.  At the correct height shown in 'exec rac'.

10) Verify the RAC in the leaderboard matches your BOINC WCG RAC.

11) Verify unbanked CPIDs get rewarded without posting daily collateral.

12) Verify the collateral requirement for RAC is correct.  You can do this by typing exec rac, verify the coin-age % req.  Issue a sendgscc wcg, then check again and verify the amount in the GSC transmission was the correct amount of escrow req.

13) Verify at the daily GSC height, the sendgsccs are automatically sent.

14) Verify GSCs are sent with an encrypted and locked wallet, from the external purse.

15) Test the ability to create a DWS (exec dws).  Verify the DWS is actually received (by recording the sent DWS amount and duration).  Verify the 'exec dwsquote' amount looks good.

Regression Testing Cases:
We also need to re-verify old features work properly:

R1) Sponsor a child with cameroon (sponsorchild authorize). 
R2) Make a post to Rob to add a simulated Payment for you (give us the check #, amount, and childid).  We will enter it into the Cameroon-One testnet simulation.
R3) Verify the cameroon-one payment amount.
R4) Verify the HEALING campaign payment amount.
R5) Add a diary entry in both the command line (sendgscc HEALING diary), test that, and also test the Send Money Diary entry.

2051
PODC 2.0 (Proof of Distributed Computing)



Welcome to the PODC 2.0 Testing thread.

In this thread we will be testing the Dash 0.14 branch with PODC 2.0:

(Please ensure your version is greater than this, otherwise your testnet branch will not sync.  We are at block 14,000 as of Nov 1, 2019).


Testnet Download Links:

Windows v.1.4.6.7+: https://biblepay.org/biblepayevo32develop.exe
Linux PC 32bits Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
Linux QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits Daemon: https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz
MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg

To self compile:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt


The ETA for MainNet for PODC 2.0 is November 30th, 2019.



CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepayevolution

Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepayevolution/testnet3 folder.




NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html




USAGE INSTRUCTIONS FOR PODC 2.0:

https://wiki.biblepay.org/PODC







2052
Hi Everyone,

So with DSQL/Christian Spaces coming out, we have a lot related to the Develop QT wallet we can test in the DSQL thread.

Im going to keep both threads open, but I invite you all to join me here for a while:
https://bitcointalk.org/index.php?topic=5188626.0

Because we will be having a new testnet develop release tonight with some new features and you all can help test those in the bitcointalk thread.

Thanks!


Ok, with PODC 2.0 coming soon, lets not use the Christian Spaces thread for testing.

Lets focus on:
-reviving our sanctuaries
-reviving our state in testnet
-ensuring we are synced
-enabling WCG miners so we can utilize the CPID and credit RAC in testnet

In the mean time, I will add a command to the develop branch that allows us to send the pro_reg Update Service command (the BiblePay way) - that takes advantage of the deterministic.conf file, so we can revive our failing sancs.


2053
Archived Proposals / Re: BBP per RAC requirement for PODC2.0?
« on: October 29, 2019, 06:17:40 AM »
another thing
if it will goes up too quickly, then it will be better to create new account than buying coins for stacking
adding new computer should be 15-20% more costly than previous one, but not 3-4x more
Seems like people are voting for 1.3:  I added a few more bonus outputs.  It doesn't look too bad for 3 machines @ 1.3, but - as a person approaches 5 - it gets exceedingly expensive, this seems to be pretty good to impede botnets.

2054
Archived Proposals / Re: BBP per RAC requirement for PODC2.0?
« on: October 28, 2019, 03:23:40 PM »
Do you think we could use an exponential function (i.e., not a static coefficient) in the calculation of the requirement?

Small crunchers would then have to stake very little for their RAC, while farmers would have to undertake serious investment.

Thats a brilliant idea; I like it, because that is mostly what all of us are trying to achieve here - more distinct users in biblepay and less botnets :).
EDIT: Im going to modify the poll based on using an exponent.




2055
Archived Proposals / BBP per RAC requirement for PODC2.0?
« on: October 28, 2019, 01:08:46 PM »
NOTE:

In PODC 2.0, we are creating an "external purse" meaning, that you can send extra BBP from your main wallet to your purse, and this purse will be used to stake collateral (so the wallet never needs unlocked to participate in PODC).

However:  Even with this nice feature, operations will work like this : either A or B:

A)  No BBP per rac is required.  No coin*age is required.  Nothing is spent from the purse day to day, and users may leave the computer off, run WCG/Cancer miners for a month, and receive 30 rewards.

Option B:

B)  Rac to the power of the exponent in coin-age is required.  The collateral amount is sent *daily* from the purse.  Although the wallet does *not* need to be unlocked, the core wallet does need to be running (and the POBH miner does not need to be running) - this is so the core wallet can send a PODC update once per day (with the collateral amount staked out of the external purse).

**NOTE** : The BBP-coin-age per RAC is actually expressed in Coin Age.  Meaning:  coins are re-used each day.  (Coins that are spent in a collateral Tx lose their coin age each day they are spent).   (But, these coins are sent back to your external purse, and then start to age again immediately).  So, a 20,000 BBP coin*age requirement means you need about 20,000 bbp~ in the external wallet continually to maintain rac rewards.

To give everyone an easy idea of exactly what the required coin age would be per exponent level, here is a chart:
The very left column is the exponent, and then we have each hypothetical RAC level).  The value after the equals sign is the coin-age required for that rac level (for that exponent level).

Exp: 1.3      500=3225.98 1000=7943    1300=11171.88 2100=20839.39 2900=31704.24 3700=43517.33 4500=56127.57 5300=69431.83 6100=83354.45 6900=97837.16 7700=112833.47 8500=128305.3 9300=144220.78 10100=160552.76 10900=177,277.84     21000=415,800     42000=1,023,821     80000=2,366,012

Exp: 1.43      500=7236.48 1300=28375.2 2100=56334.39 2900=89377.69 3700=126627.63 4500=167530.5 5300=211696.9 6100=258834.2 6900=308712.49 7700=361145.11 8500=415976.76 9300=473075.67 10100=532328.31 10900=593635.54

Exp: 1.56      500=16232.79 1300=72069.52 2100=152286.74 2900=251965.38 3700=368463.68 4500=500047.8 5300=645461.52 6100=803738.08 6900=974102.33 7700=1155914.02 8500=1348632.2 9300=1551791.61 10100=1764986.32 10900=1987857.9

Exp: 1.69      500=36413.24 1300=183047.7 2100=411671.32 2900=710317.67 3700=1072163.24 4500=1492550.89 5300=1968005.1 6100=2495786.44 6900=3073653.9 7700=3699723.99 8500=4372380.86 9300=5090215.66 10100=5851983.89 10900=6656574.26

Exp: 1.82      500=81681.82 1300=464918.58 2100=1112856.37 2900=2002462.34 3700=3119802.76 4500=4454990.43 5300=6000425.98 6100=7749974.97 6900=9698517.31 7700=11841674.52 8500=14175632.47 9300=16697019.96 10100=19402822.03 10900=22290316.05

Exp: 1.95      500=183227.86 1300=1180835.87 2100=3008344.89 2900=5645157.92 3700=9078066.55 4500=13297328.62 5300=18295233.04 6100=24065405.19 6900=30602416.87 7700=37901545.03 8500=45958612.12 9300=54769874.99 10100=64331944.54 10900=74641725.59


So for example, if you vote for a 1.69 exponent, this means a researcher will need 183,047 in coin-age to be rewarded for 1300 RAC.
A researcher will need 6,656,574 in daily coin-age to be rewarded for 10,900 rac. 

NOTE: If a user does not have enough, we reward the capped amount: for example if they have 36413 in coin age, the exponent is 1.69, their rac is 1500, they will receive a reward based on 500 RAC for that day (IE the capped RAC for their coin-age level).





Pages: 1 ... 130 131 132 133 134 135 136 [137] 138 139 140 141 142 143 144 ... 263