Bible Pay

Recent Posts

Pages: [1] 2 3 4 5 6 7 8 ... 10
1
BiblePay
1.4.7.8 - Mandatory Upgrade for TestNet

- Require depth of at least 1 for new DWS stakes, Enforce DWS max limit in every area to ensure the burn can't enter the chain resulting in an overlimit condition (and include memory pool totals)
- Add spork rejecting new child sponsorships when there are none available

** This is the windows release; the rest will be compiled soon **

2
Hey Rob and MIP,

Im trying to download
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz
But I think its a 0kb file right now?
Tested on Ubuntu with wget and downloading through web browser on Windows

I've got one for deployment coming in a little bit; so we can keep testing DWS; let me finish it up tomorrow morning and then we can redeploy.

3
Windows v.1.4.6.7+: https://biblepay.org/biblepayevo32develop.exe

what is 32?
4
Ok everyone please stop testing the DWS burns until the next version, I added a couple more rules.

Lets test everything else.


For PoDC 2.0, I was thinking of hopping back and forth between team BiblePay and another team (GRC or OByte). Was thinking I could time bouncing back and forth somehow to double dip.


Just thinking back to the days where PoDC users shifted BBP between wallets to perform their PoDC updates and stake far less than required. I think you are using coinage somehow so the wallet shifting wouldn't work, but still trying to figure out any potential exploits.
5
Hey Rob and MIP,

Im trying to download
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz
But I think its a 0kb file right now?
Tested on Ubuntu with wget and downloading through web browser on Windows
6
So I updated the test cases in Post #2.  Please let me know if you all can think of any more test cases reqd.  You can also execute the test cases that we have not executed.

I also started an unbanked researcher with 90 rac. 

7

We could probably prevent this by requiring coins with at least 1 confirm for DWS.

Let me look into this.

Ok everyone please stop testing the DWS burns until the next version, I added a couple more rules.

Lets test everything else.

8
If we repeatedly send dws - there's no way to prevent this message? I can foresee a lot of tech support around this. You can tell people to send only one tx, but you know that will not happen. With PoG v1, people sent multiple tithes in a block... same scenario here.


2019-11-21 13:44:39 ERROR: AcceptToMemoryPool : Transaction b869f42c5188368c5f9a8541b48f384e6bbf79fed89f7d38f437161bc731956e conflicts with completed Transaction Lock ef650256b9e1d1fcb79f138f53baa5220bdc28d13f0c42dfce5db0eab4360616
2019-11-21 13:44:39 CommitTransaction(): Transaction cannot be broadcast immediately, tx-txlock-conflict


We could probably prevent this by requiring coins with at least 1 confirm for DWS.

Let me look into this.

9

If we repeatedly send dws - there's no way to prevent this message? I can foresee a lot of tech support around this. You can tell people to send only one tx, but you know that will not happen. With PoG v1, people sent multiple tithes in a block... same scenario here.


2019-11-21 13:44:39 ERROR: AcceptToMemoryPool : Transaction b869f42c5188368c5f9a8541b48f384e6bbf79fed89f7d38f437161bc731956e conflicts with completed Transaction Lock ef650256b9e1d1fcb79f138f53baa5220bdc28d13f0c42dfce5db0eab4360616
2019-11-21 13:44:39 CommitTransaction(): Transaction cannot be broadcast immediately, tx-txlock-conflict



10
Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Last post by Rob Andrews on November 20, 2019, 08:33:16 pm »
All, lets please test instantsend thoroughly, lets verify the quality of IS is what we expect for prod in testnet?

Pages: [1] 2 3 4 5 6 7 8 ... 10