Messages

2566

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 04:38:14 PM »

I've chceked my txs and i looks, that this is my only missing reward.
Thanks for explanation.

Great, please let us know if our accuracy maintains 100% over the next few days.

We are now in qt-level 4!  This is great.

Thanks to all participants!

2567

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 04:35:15 PM »

Whoever is sending donations of 666.66 to the orphanage foundation, I rebuke your donations in the name of Jesus.

I hereby command and bind up demons assigned or attacking this project to go now to the deepest part of the abyss and stay there until Jesus deals with you.

2568

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 02:00:59 PM »

How to check last payed GSC rewards?
I have 3 GSC transmission txs 20h ago, but no reward.
those txs:
571a2ccd45cb1adf4231765e03b3357bd92a626973fab422fe119b8b9ccc1cd1
4bca9b0487a6bb597bdb6d223c095dbf2b63a2ee7626bd78fc17bbc8d42ecbb5
bb0c5c85d39ca7c30b6f732a543f2d7a00491a8d2e3f367e0d678a20a659ec5a

So if we type 'exec points txid', I see 25 million points accrued across the sum of these 3 tx's, and the height was 25470 as of the transmission, meaning the next superblock was @ 25625.  (height % 20 + 205 arrives at 25625).

So doing the 'exec prominence false 25625', I see the chain assessed you at 21 mil in that superblock.

So far everything is good from the Accrual side.

Then we do a getblock 25625, and getrawtransaction 03e4* to look at the coinbase, and woila, the problem is that block became a regular block (not a superblock).

We do have a rule in place that will delay the superblock up to 15 minutes (in case sancs are coming to consensus at that time), so I think whats happened here is this is the height where I deployed a mandatory upgrade and everyone upgraded and overjumped this block (IE it took more than 15 mins to upgrade, so a normal block was allowed, and the sancs were down).  I believe this will be the case if this is the *only* missing block-payment, as I have been watching the last 10 superblocks and historically the last few days of blocks and they are all emitting fine as long as the sancs vote on the supermajority. (See exec health = 4 votes almost every single new sb height etc).

Another words in prod, this would never happen, unless we have half the sancs running on a conflicted version and they all disagree.

Is this your only missed payment?

2569

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 12:43:51 PM »

Can this be increased?   10 Characters can run out rather quickly once we get more main-stream adoption

No, but people will receive a message letting them know its in use.

10 is enough for 20,000 users or so, that should get us to the next platform version, then we can discuss changing.  We can also discuss it if we have 20,000 by the end of the year as I will have quite a surprise by then as long as we are priced over 14 satoshi at the time.

2570

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 09:07:14 AM »

So QT (Quantitative Tightening) has now been turned on in Evo (In testnet only).
We are in Day #1.
Fortunately in testnet, we have the equivalent of 4 superblocks per day, so we should transcend from QT level 1-4 in one day.

Lets keep an eye on the chain, make sure it does not fork (I deliberately have not turned on any other layers yet).
We have a difficulty of 12, that is a good indication the chain is healthy.

Lets keep an eye on our daily superblock budget and our monthly budget also, and see that it remains stable (its now based on *last* months budget - IE 6000 blocks behind where we are now).

To see the qt level, type exec price, or look at the overview page in biblepay-qt.

2571

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 08:59:12 AM »

Btw, our last Monthly governance superblock did pay out the rewards correctly.

I see someone has in an orphan sanctuary proposal, good, please monitor it to make sure it pays (and you receive the payment) when 27265 occurs.
I will enter a few more proposals now, but lets ensure we vote your Orphan Sanc up, and monitor the highest votes descending are included for payment.

2572

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 08:53:38 AM »

1.4.1.6-Mandatory Upgrade for TestNet

- Limit nickname length to 10 characters

2573

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 12, 2019, 06:48:56 AM »

emm, I have differnet hash on that block like yesterday-

10:31:55

getblockhash 25354

10:31:55

ce7fbfd5dfbab275f35984dac4b447db7866d1bd38eac7c19010764b1f603085

Yes, that matches mine, that is normal, we were reorganizing when I posted that hash yesterday and everyone was upgrading.

2574

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 03:08:12 PM »

thats why I am stuck at 25237 after re-sync.
 019-04-11 19:45:03 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=436 seen
2019-04-11 19:45:03 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=436 seen
2019-04-11 19:45:27 SPORK -- hash: 0b55391d2c25736279fb64125f046026b833b7021b00cafb296dcd287b72106f id: 10008 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=5 seen
2019-04-11 19:45:27 SPORK -- hash: 0b55391d2c25736279fb64125f046026b833b7021b00cafb296dcd287b72106f id: 10008 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:27 SPORK -- hash: 00f31f1feb64a49df40213e52e3e3ce2191e6f19f6241a1740043f08efdb1ba6 id: 10011 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:27 SPORK -- hash: 644278d68318691dc8f02c6f714a12eaf27a63764caf590fc8aaeb6118725051 id: 10090 value:          0 bestHeight: 25237 peer=6 seen
2019-04-11 19:45:29 ProcessMessages(version, 109 bytes) FAILED peer=558
2019-04-11 19:45:29 ProcessMessages(version, 109 bytes) FAILED peer=559
2019-04-11 19:45:33 ProcessMessages(version, 109 bytes) FAILED peer=561
2019-04-11 19:45:39 ProcessMessages(version, 109 bytes) FAILED peer=562
2019-04-11 19:45:41 ProcessMessages(version, 109 bytes) FAILED peer=563
2019-04-11 19:45:42 ProcessMessages(version, 109 bytes) FAILED peer=564
2019-04-11 19:46:17 ProcessMessages(version, 109 bytes) FAILED peer=565
2019-04-11 19:46:24 ProcessMessages(version, 109 bytes) FAILED peer=566
2019-04-11 19:47:07 ProcessMessages(version, 109 bytes) FAILED peer=568
2019-04-11 19:47:19 ProcessMessages(version, 109 bytes) FAILED peer=569
2019-04-11 19:47:22 ProcessMessages(version, 109 bytes) FAILED peer=570
2019-04-11 19:47:52 ProcessMessages(version, 109 bytes) FAILED peer=571
2019-04-11 19:47:53 ProcessMessages(version, 109 bytes) FAILED peer=572

The failed messages just mean we hang up on peers less than our version (they have not upgraded yet).

We solved about 5 more blocks after the 20 diff block, but Im still waiting for warnings to clear.

I think everything is ok, but lets solve a few more and let the warnings clear first then we can try another diary entry.

2575

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 02:18:33 PM »

Seems that all my sanc are went out of sync and are unable to sync up to that block. Stuck at 23234 when I initially got one sanc to sync with your 3 even after resync.

isn’t the ABN feature supposed to prevent these sorts of attacks? Please help me understand in layperson terms what is happening and how did that bypass ABN?

Thank you.

1) We had synced from 23234 up to about 23336 but with a difficulty of .10 (IE very low).
The wallet will reorganize back to 23234 if it finds a chain with greater total chain work (which is possible since 23234 had a diff of 20.)

(As long as the re-org block is valid).

2) ABN tries to prevent single rich kiddies (IE someone who has 20 servers) from solving an inordinate amount of blocks personally.  It does this by using up their coin-age.  But in testnet this 20 diff could come from a few high powered machines, although more likely 4-5 miners running full speed right up to that block (so you are correct abn might have helped, but in testnet everyone has a lot of coin age also).

2a.  We actually don't have ABN turned on right now , I disabled it so we can test one feature at a time.  I planned on enabling qt next then abn later, but now we have to figure out this sync problem first.

3.  I am also rolled back to 23234 right now, so you are experiencing the same thing as me (another words the hash I posted is no longer valid).

Ill do some poking around.  We probably need to turn up our miners to more threads to solve the next block.

2576

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 01:55:38 PM »

We will have to be a little patient as we have most likely Slovakia playing games - the diff is 20 now in prod and chain is reorging. 

Im sure it has nothing to do with Evo or the latest version, because the mandatory height hasn't hit yet.

I see we rolled back when this person who tithes 666.66 hit us with big hash.

2577

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 01:21:13 PM »

this one is the sameon my side :

20:16:32

getblockhash 25354


20:16:32

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd

But when you pasted your log it shows a bad hash here:

2019-04-11 16:59:39 UpdateTip: new best=0368d885bd5aa5517ede5ff01bf470a270ad63e79df5154f3e2d39cb960e744a height=25553 version=0x20000001 log2_work=44.48151079 tx=81668 date='2019-04-11 1

Did you resync just now?

2578

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 01:02:01 PM »

Nothing happens, well no error, it just clear everything out.
I am using QT, desktop version. Unless I am doing smth wrong.

I have a different hash for 25553.  I am pretty sure some nodes banned each other (due to the mandatory), could you please rm chainstate -r rm evodb -r rm blocks -r rm banlist.dat, and resync and see if your hash matches the one from a few blocks earlier - then please retry the tx? 

Then also see if you can scrape the txid out of the transaction double click, and also, it should have the diary entry at the very end of the window.

I think we are on this blockhash :

09:03:54

getblockhash 25354


09:03:54

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd

2579

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 09:05:44 AM »

6) is it working? because it doesnt make a transaction. -diary entry
If you check "Donate to fundation" is the same address and it make a transaction.

Yes.

Please post the error you get, as we bubble the error to the screen in QT (are you using QT)?
If no error on the screen its also written to the log.

EDIT: Also, please post the diary entry here, so I can reproduce.  It must be > 10 chars in length to be valid.

2580

TestNet Discussion Archive / Re: TestNet - BiblePay-Evolution & GSCs (Generic Smart Contracts)

« on: April 11, 2019, 09:04:22 AM »

I think we are on this blockhash :

09:03:54

getblockhash 25354


09:03:54

72887c9dec86fe2cc3c97ef7caa3691505c81adbb021af177fd34088c72fdbfd

(Some nodes got banned as we upgraded etc).

Diff = .41