Messages

2746

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 23, 2019, 05:21:44 PM »

I am on the same...
I'm stucked on block 110107. I've tried reindex and rescan but "?" txs are still there.
My tithes are going out but didnt show on pog leaderboard.
BTW: Rob POG leaderboard looks with highlight good now

Thanks- this version was a dud!

2747

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 23, 2019, 05:21:01 PM »

i tried with -zapwallettxes=1 and then tried the more destructive -zapwallettxes=2 ... The tx with the ? disappeared, but then new ones are appearing. I already lost all my coin age with zapwallettxes=2 but I may have to salvage my wallet.dat and blow everything away and start over.

1) Ive never used zapwallettxes=2, also, I dont recommend it.
2) You dont lose coin age by rebuilding your wallet.

2748

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 23, 2019, 05:19:43 PM »

I did that


18:17:21

getblockhash 110000


18:17:21

f45a1ce036cc0e5e0edf5ca4ccf2086248b307c0dbdc1fe2fcc818e5b100e503

now 10 hours out of sync restarted several times but still out of sync

Oh your right, sorry.
So looking at the problem, my fix for this mandatory version did not work (another words it wasn't the rounded payments that was the problem).

I believe the problem has finally revealed itself (I cant guarantee this is our 'last' mandatory upgrade), but we do need another upgrade.


Im building windows now... Please hang on; it should be ready around 9 pm CST.

2749

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 23, 2019, 12:07:49 PM »

Can anyone confirm that they have testnet running as I am showing out of sync by 4 hours as of posting this.

Only transactions that seem to be happening are outgoing nothing incoming.

Here is the hash:


12:07:36

getblockhash 110000


12:07:36

f45a1ce036cc0e5e0edf5ca4ccf2086248b307c0dbdc1fe2fcc818e5b100e503


Yes, all my nodes are synced with 5 pog participants.

As far as "?" marks in your tx list, that means you havent cleared your orphan tx's with -zapwallettxes=1 yet.

2750

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 22, 2019, 06:37:32 PM »

Thanks. Is there any guide for IPFS server? Is it just usual IPFS server or it needs some special thinks for Biblepay?

I've asked Slovakia to test his acces time to Business lists and his experience is very similar.
He even tell me that orphan list didnt show (but for me it is with time more than 60s so maybe he didnt wait enough
So it definitelly looks to problem with servers in US and it's too far for us (with latency).
I've found that IPFS server is 207.148.5.184:8080 but I wasn't able to test access times because it loks that PING is blocked
But through page https://www.dotcom-tools.com/web-server-performance-test.aspx I've found access times from different world locations and it looks that avg access time from Europe is 300ms which is very similar to my peer list avg ping time. So it looks that most of my peers are from US

Thanks a lot.

So running an IPFS node in Slovakia is not too hard but it does require a few things not out yet (but are almost out).
The IPFS node requires some changes to the config, it requires a swarm key (this means the node only talks to biblepay IPFS nodes and saves disk space for BiblePay only files), IPFS DNS server, and potentially some type of IPFS reward from the future Christian superblock payment (thats the part not done yet).

So before we can actually deploy one we need to write a Wiki explaining this and release the DNS and swarm key at a minimum.  Ill keep you updated as this gets closer.  Im going to try to get this phase completed by March 30th 2019.

2751

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 21, 2019, 12:26:35 PM »

1.1.8.3-Mandatory Upgrade for TestNet


- Highlight user in POG leaderboard UI
- Fix bug in POG block checker (IE compare rounded amounts) before
failing a block
- Add POG Leaderboard to toolbar menu

** Note:  Please upgrade as this version hangs up on old clients **

2752

Archived Proposals / Re: Re-Enable Team BiblePay Requirement in PODC

« on: January 21, 2019, 10:47:50 AM »

So, can you explain exec podcupdate in more detail?

It seems like every PoDC update re-adjust my PoDC input to an output with UTXO target and a change address. Does that mean that PoDC coin age updates to 0 coin age?

There's only only BBP address for a CPID right? So, if I need to stake more in my wallet for 100% PoDC payment, couldn't QT wallet send non-PoDC balance to a new PoDC balance don't destroy the coin age of other PoDC balances? That way, you know the coin age of each balance. You exclude min coin age < 1.5 day (to prevent wallet hoppers that exec podcupdate once a day), and you do the math from block 1 to now for all the inputs & ouputs of the PoDC balance?

We take the average age of the spent coins to assess the avg_coin_age.  If its < .50, its not a valid utxo update and not acknowledged by the sanc to be valid (IE its skipped).

The actual address does not come into play.

Once you spend those coins they lose the coin age.

2753

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 21, 2019, 08:10:57 AM »

** Very Important Alert **


So while getting ready to create a release candidate for prod, I started checking the logs, and I found one problem in POG - don't get too alarmed, it's minor, but requires another upgrade and another round of testing unfortunately.

There were two blocks that were rejected by everyone - that fortunately has enough forensic evidence in the log for me to see whats 'potentially' wrong.  (That will be a challenge to fix this in one release), the issue appears to be a rounding issue in satoshi, when we reach a scale of more than 4 digits (for each pool recipient).  What I plan on doing is making the pool round off the payment amount and making the blockchecker check the rounded amount.

Sorry for the inconvenience but we must go through this to create a quality product with no errors in prod.

Please, keep your eyes peeled and upgrade as soon as possible so we can potentially wrap this up before the end of January and have our mandatory upgrade.

The new version should be ready in about 4 hours or so.

2754

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 21, 2019, 08:01:24 AM »

Thanks. I thought he said 5 seconds, but 5 minutes... you're right is too long of a wait. I'm not getting that at all.

Short term, could he run IPFS node locally and see if it helps with response times after IPFS node is synced up?

I posted in #372 (right before your post #373) the answer in the 2nd paragraph.

2755

Archived Proposals / Re: Cameroon One 2019 Quarter 1

« on: January 20, 2019, 05:44:27 PM »

The situation with Compassion is unfortunate,
Much rather the funds go to someone who will work with us like Cameroon One!
Voting yes

For those new or who have forgotten, here is the original proposal a year ago by Cameroon One:
https://forum.biblepay.org/index.php?topic=86.0

Yeah its pretty sad when we asked to run an ad campaign that Jaap and April were writing and we were told No we will not receive any authorization to use the logos and No to collaboration in general.  (At the height of our mission with over 300 orphans).

The other issues are even worse.

2756

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 20, 2019, 05:36:15 PM »

Thanks Sunk.
I've tried Sysinternals Process Monitor to catch some other processes affecting biblepay-qt.
I've found only my antivirus, but after stopping it the result was the same (reading avg times were from 5s to 15s).
I've tried it in Windows' safe mode, but it was still without change.
I'm sorry, but I'm not able to find root cause.
I've tried it on different PC and the results was same... But it was still on my network.
Maybe there is problem with my router or provider.
But I haven't problem to watch 4k streams and download 40MB/s (like I said I have 500/30 Mbit network - but on my PC I have ony 100Mbit)
Let it be. It realy looks that it's only my problem, but I don't know where.
Maybe it's problem with long distance to USA
I have download speed problem with wallet from biblepay.org too.
The download speed is sometimes too slow (maybe 1MB/s - now I tested it and it was 3MB/s).

Right, then I can explain this situation for your LAN pretty easily.  Knowing that the business object list is chatty (meaning it has to ask for each business object IE one row per object), that means latency is an important factor.  Knowing that my original question (of how fast is your WAN speed) has an answer of about 1MBPS, which is very slow, that means my answer would have been :  Your WAN has high latency and is slow - because all our IPFS nodes are in the US.

You either have to increase your US wan speed or run an ipfs node in Slovakia.  Dont jump on the Slovakian node too fast though because one of our other intermediate IPFS goals is making an IPFS DNS server with a swarm key and thats not done yet, so no sense in trying to hurry and volunteer for one in your region yet.

2757

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 20, 2019, 08:36:50 AM »

However note that I still believe its a one off - because I tested from 7 machines around the world over 3 networks and 2 oss.

So it is important for Orbis to run his test from a different PC and then isolate the problem on the first pc.
(I did offer an explanation as to how to isolate the IPFS links in a prior page).

Regarding the "some delay" comment thats because 100 business objects are equal to 100 IPFS calls - therefore yes there is some delay (but not more than 5 seconds).  Orbis said 5 minutes, which is clearly an HTTP timeout on his PC for certain calls.

The main thing I caution is to not try to blame biblepay for something that is broken on one persons machine.

2758

Archived Proposals / Re: Re-Enable Team BiblePay Requirement in PODC

« on: January 20, 2019, 07:19:41 AM »

Oh, and I just realized this is the wrong solution to the problem. You know why?

BM9hu373mUL4o9NiPB5j48jtD8oZomiUDU just needs to join Team BiblePay. Worst case, he can't earn GridCoin (which pay less anyway per RAC), but s/he can still earn ByteBall (now OByte). So, if you are motivated by greed, the logical step is to join Team BiblePay since BBP pays better than GRC. In the end, you piss off many people and you still have a cheater doing PoDC.

We have a Phase 2 & 3 solution also though we can add in if this continues to occur.

TheSnat is monitoring the problem; if its more than 20K~ BBP a day we consider it something we need to mitigate (as I dont know if PODC will really be around for an extended period, is what I mean).

But anyway, we enabled the spork today that enforces coin-age in UTXOs.  That will affect *some* of the network and sancs by itself.
After this vote ends, we will keep re-assessing.  If the problem is still severe in 3 days, we will ask the sancs to upgrade so as to enforce coin-age early.

Another words, we don't tolerate this and will react now.

2759

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 19, 2019, 04:37:11 PM »

Business object list loads fast for me on  testnet & prod (1-3 seconds)

Thanks.

2760

Archived Proposals / Re-Enable Team BiblePay Requirement in PODC

« on: January 19, 2019, 04:25:52 PM »

I recommend that we hold an emergency vote that Proposes that Team BiblePay be REQUIRED to participate in PODC  rewards (in contrast to having no team requirement).

The reason for this is TheSnat has discovered that 5 Gridcoin users are sharing UTXOs by sending them back and forth to each other more than once per day.

Although we have a feature to Stop this behavior, the spork is not fully enabled in prod because it would require a mandatory upgrade (to ensure all of the remaining sancs honor this setting).

In the mean time I feel it is highly unfair to leave this activity unchecked at the expense of our core team.  (The activity is penalizing small users rewards at the expense of the bad actors).  (We estimate the ill-achieved UTXOs to be rewarding 20% of the PODC budget per day.)

Therefore I recommend that we vote in the Team Requirement to be REQUIRED again within 48 hours.

Secondly, we have been very patient, and the original idea behind Not requiring the team was that BiblePay would grow in popularity by reaching the mass of boinc users.  IMHO, it clearly has not had that effect.  What we have observed is a few very large users (I am told Turkish) have been hogging the top rewards, and we have seen stagnation.  This is actually driving away our smaller users.

Thirdly, our PODC difficulty level has not increased since we removed the team requirement, it has decreased.

In light of this I recommend the sanctuaries consider these factors to vote the way you feel would be best for the community at large.

Vote YES for us to REQUIRE TEAM BIBLEPAY to participate in PODC.

Vote NO for us to leave PODC as is and Not require a particular team.