Messages

2896

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

« on: December 19, 2018, 11:59:28 AM »

Why did this wallet get POG rewards?

Code: [Select]

"Confirmed","Date","Type","Label","Address","Amount (tBiblepay)","ID"
"false","2018-12-19T10:14:08","Mined","","yW8TrtjNKAAvxh5z2yqYJGiDMdnTvGC8yz","485.50457678","b9256094d79e3c15c2aaa9fea17c31f79ca962113b82c57d2e231d49e1a353a9-000"
"false","2018-12-19T10:07:05","Mined","","yW8TrtjNKAAvxh5z2yqYJGiDMdnTvGC8yz","4854.80305666","a2ce916f12ffc3ef038c9e31e197eb40b4b3199e7f5e25490631691c94f2d109-000"
"true","2018-12-18T23:36:33","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.38318243","45219e8ca515f77560d821b3e119eff1b0dc80d4011acf9887d477d56b57c693-000"
"true","2018-12-18T23:34:17","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.43174017","1dd063ec8243f52d8a04c22a4b0fd39c57711fcb3805e1d7efc3616474424aba-000"
"true","2018-12-18T23:30:24","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.48030567","f1541dfab2c02e169bad57a34b2e9f5ddb3784e077e74ca5d39cd38467c0916a-000"
"true","2018-12-18T23:23:07","POG Reward","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","97.09605959","085dc568b321102faa15c3269fa66fa4de84edade402f52026a64168890103cc-000"
"true","2018-12-18T23:17:45","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.52886271","99a8779cd51518a8f3c63fff4e76e445165a9dfbf4b60a44940d78d74e75d547-000"
"true","2018-12-18T23:17:28","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.52885565","d57eeff95645d26559469d49e2b76cbea2e2e98e5bd727d79adf9b229a936874-000"
"true","2018-12-18T23:00:42","POG Reward","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","97.06693200","4e6c7909383f9f4156974cac9be833decfc1b2d0571a27843240a949eb5e5baa-000"
"true","2018-12-18T22:54:49","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.38318243","c99c37942b2298aa675339b6570486dc9750e382412952f2fd22beadeef90417-000"
"true","2018-12-18T22:44:39","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.50457678","a20ef209138ba63c15a0fe4cb6c24a14ace68c89f87796b59379bde09adb45e5-000"
"true","2018-12-18T22:38:43","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.45604228","7df4ea97f8c37091667a61dc96c323957f14c5598a01ad8860227a28ba786344-000"
"true","2018-12-18T22:19:22","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.43174017","9b6a9bea9cdee042da3c5198114a0aa4b8f0668d2e68b241d156649a24fb76d5-000"
"true","2018-12-18T22:15:22","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","4855.28855647","08e6dbcdc9c6055816ba1832b449a304611a82f154e7240daedcc1db049f76d1-000"
"true","2018-12-18T22:14:42","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.50457678","1bfd91d5a2aaeb5676ef1d73ebff7c418ed1c4860d93ed67bb65da3e23409b5b-000"
"true","2018-12-18T21:58:28","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","4854.07461294","571544886393109ed674ad4bc972fbdc5d38b45f71c6081c5740372de6c13068-000"
"true","2018-12-18T21:49:14","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.45601904","ae36f2d9f75cd028f8951caf739e0fa975093b25fe5f64a24ad6f02f690b8278-000"
"true","2018-12-18T21:48:45","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.40746130","14e9f71c3b97766bed06446b3432857c6d3485ca8aafa6650362161eb7b228e5-000"
"true","2018-12-18T21:23:10","Mined","","yeA8AZunKHTPUQD4Dibe1MeVFbomg1U7Qc","485.40746130","2a1083542b1eea9620a95112780ee29072d26a1702ef895f2a4283409d0a535b-000"
"true","2018-12-18T21:22:01","Received with","","ydmznuZ1cHvCSnSLZ9pZg8Tgou8Ar2XjTW","10000.00000000","7c52dfa77116a625bb915df17bdb21628b4d58b447ec1b694f7a2446cb0f56a4-000"


Thanks for the example.  On a side note we have a feature in the next version that will allow you to type exec pogpool height, and diagnose some of this , although that feature is broken right now in your version.  But anyway looking at your wallet and its rewards, you received the first POG reward on block 91097 for 97.09 bbp. 

So here is what happened:  Those two pog rewards are incorrectly listed as POG reward on the UI.  They are actually mining rewards.  If you look at the actual transaction, the 97.09 was the reaper reward for solving the block .

So I see the bug, and its being fixed now (as far as the display issue).  Please double check in the next version that we killed it - those two should change to Mining rewards when you boot the next version.

2897

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

« on: December 19, 2018, 11:14:18 AM »

my config:
addnode=explorer.biblepay.org
testnet=1
genproclimit=1
nickname=slovakia


still running prod, no testnet ... where is problem? after installation v168 i have this problem with testnet wallet 

thanks for help

EDIT:  If your wallet is booting in prod mode do this:

./biblepay-qt -conf=biblepaytest.conf

Save your testnet config file as biblepaytest.conf in the ~/.biblepaycore directory.

EDIT: Dont forget to add your tithe parameter.

2898

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

« on: December 18, 2018, 05:45:17 PM »

Are biblepay-cli.exe and biblepayd.exe supposed to work correctly?
I have a feeling that some tithes are not working as I think.
For example if I take max amount from

Code: [Select]

exec titheinfo and then run

Code: [Select]

exec tithe <max>. I can see from debug.log that tithe was illegal.
What happens those bbp? Why max is illegal?

These might not be your tithes; Ive been trying to break it - the log is actually a log of everyones activity.

So I just tried it and mine was legal;

Could you please try it again and copy the txid, then type

exec istithelegal txid

After a couple blocks later, and that should show if it was truly illegal or legal.  Also in the log you should not see your amount (or block #).

PS: To answer about where the tithe went, yes, the tithe would have actually gone to the foundation and have been spent; so yes it is critical to ensure we verify this bug does not exist.

Ive been monitoring for PogRecipientsInvalid, and to my happiness that appears to be fixed; and the Illegal Tithes from today "should" have been mine.

Lets try to break it.


EDIT:  You should be able to go back in your txlist for the one you sent at the time of the post, and grab the txid and lets double check that one.

'exec istithelegal txid'

2899

Archived Proposals / Re: Use Togo's Bitcointalk ANN Redesign

« on: December 17, 2018, 06:05:51 PM »

To be clear, I think the content of the main post in togo's ann thread is what he wants moved to the main ANN
not replace the existing ANN altogether.

Yes, I am looking at it tonight.  We might be able to include the best parts of it.

However it would be nice to know that Togo is on the Godly side of our mission (in contrast to the derelict side) therefore I would still like the questions answered.

2900

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

« on: December 17, 2018, 03:33:42 PM »

1.1.6.8 - Mandatory Upgrade (TestNet)
** Note: This mandatory will only disconnect old versions, but will not hard fork so as to keep the chain running smoother
** Forensically we now have more specific logging with the version in the POG message


- Fixed crash bug

2901

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

« on: December 17, 2018, 12:48:56 PM »

So I started to run a few basic calculations last night regarding scripting attack vectors (in relation to potentially needing a guard in the program to charge exponentially increasing tithe fees when under attack) (as I was considering adding a fee to each donation transaction vout > qty(10), increasing from 1bbp per 1bbp per vout and rewarding this to the reaper) and I quickly came to the conclusion that we dont need it  - because the number of transactions taken in the pool causing the diff to govern the problem is very small.  If a whale tithes just 100 times in a block, the legal tithes (approx 280,000bbp) would raise the diff by almost 50% on the very next block  - mitigating the problem immediately.  The other issue is, we dont want to hurt newbies.  A legal tithe is a legal tithe if it fits within the difficulty params.  So I feel simplier is better, just leave it out.   (On a side note, the size of a transaction for small donations IE attacking us with 1 bbp tithes can be mitigated with increasing tx-relay fees - which we definitely need and will definitely implement as of next mandatory).

Besides this we have our normal transaction fee (which btw I found a bug in last night) - it is approx 100* too low - I made some notes in the code about a 130 input transaction having a fee of only .003 that should have been .300 bbp.  If we "fix" our minimum relay fee, this should also discourage tithe attacks, as the size taken up by the transactions will quickly increase the cost of each transaction with normal BBP fees of 2bbp, 3bbp, 5bbp etc as the block size grows.

So I feel we have our bases covered regarding tithe attack vectors related to scripting.

2902

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

« on: December 17, 2018, 12:38:02 PM »

Also available in Linux PPA repository
sudo add-apt-repository ppa:biblepay-official/testnet

and MacOS
http://www.biblepay.org/biblepaycore-testnet.dmg

Thanks for building this.

Note everyone, I found a bug in 1167 that will crash the node during mining.

1.1.6.8 is building for windows now.

2903

Archived Proposals / Re: Mass Adoption for BiblePay II

« on: December 17, 2018, 10:14:33 AM »

I can appreciate the complexity of pobh podc and pog coexisting. If I read your last post right you want to remove podc altogether? That's a bit much and I think pog podc combo is better. Or all three (pobh podc pog).

Podc is has big participation rate so it deserves a slow curve to reduced payments. Maybe if there are sports to pobh podc and pog rewards the rewards can be tweaked slowly.

Big changes scare of investors.

 This is partly why I asked if pog rewards can contain send bbp transactions as well.

It was made clear that the sanc poll for the ideas acceptance was to replace all of our mining algorithms with pog (for easy adoption).

I'm definitely thinking we would go through a full test phase with POG as the heat mining algorithm, and PODC still existing.  POG gets the heat payment rewards.

Yes, a lot of things scare investors, including stagnating by one user a day and relying on an oracle.

I'm open to ideas about how POG + PODC could coexist (maybe 20% emission to PODC, 80% to pog) for example.  (I would not talk about POBH by itself - its being replaced by POG in testnet and its underlying technology is definitely POBH).  However even if PODC lasts a while, it doesn't make sense to pile massive infrastructure and support into something that might go away.  The moment it breaks, if POG is doing the job then maybe PODC should be retired at that point.  Who wants a half finished UI with broken parts for easy adoption in the PODC if its not going to be used fully.  So imo, the test for POG (as far as easy adoption) should be taken very seriously, and if it works that way (1 new user + per day) then I would consider the next logical step Removing all the unecessary IT code, and becoming a gospel coin like we should be doing in the first place.  Like putting some preachers in the wallet and preaching to users, and a Getting Saved button for example.  And a Getting Saved chat room.  Who will do all that if they are spending all day supporting scientists?


I don't know what you mean by "send transactions with pog", could you explain that in more detail?

2904

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

« on: December 17, 2018, 10:02:49 AM »

1.1.6.7 - Mandatory Upgrade (TestNet)
** Note: This mandatory will only disconnect old versions, but will not hard fork so as to keep the chain running smoother
** Forensically we now have more specific logging with the version in the POG message

- Fixed 'exec tithe' to allow just amount
- Added low and high estimated ROI to 'exec titheinfo'.  Note:  The ROI is based on: Daily_POW_Rewards / TitheCap, divided by 2.  The divided by 2 is assuming the miner spends half of the profit on electricity.
- Removed non-biblepay-team warning in exec getboincinfo
- Fixed the PODC Reward and POG Reward "clock" symbol to require 120 confirms in the UI transaction list
- NEW USER SETTINGS:  Made the wallet Not tithe automatically by default, unless the 'tithe=1' setting is set (or user uses the one-click mining configuration setup).
Possible settings:
Missing = Wallet will not auto tithe
tithe=0 or -1 Wallet will not auto tithe
tithe=1 : Wallet will tithe automatically according to default network SPORK (once per 4 hours in prod, once per hour in testnet)
tithe=NN : Enter any number in minutes above 2, and the wallet will tithe this often

- Added POG Difficulty to overview page

2905

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

« on: December 15, 2018, 06:14:17 PM »

the above command isn't working for me in the debug console.

12:52:24 exec tithe
12:52:24 You must specify amount, min_coin_age (days), min_coin_amount.  IE: exec tithe 200 1 1000. (code -1)

12:52:27 exec tithe 250
12:52:27 JSON value is not a string as expected (code -1)

Good find, I just added this to the bug list.  Working on it.

2906

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

« on: December 15, 2018, 06:12:15 PM »

Is there a frequency that is observed for "tithing"? TestNet seems to be about once an hour. If I were to tithe 30 minutes after an automated send, that is considered an illegal tithe?  If the transaction is not created, it wouldn't be in the "unconfirmed" stage. Unconfirmed seems like it would encourage more confusion to new users.

No you can manually tithe as often as you want and it wont be illegal - as long as its a legal tithe.  Legal means it fits the difficulty parameters.

If it were any other way people would try to game the system by writing scripts to tithe.

The frequency is once per hour in testnet.

Im making it so you can override that in the settings next.

2907

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

« on: December 15, 2018, 06:10:48 PM »

I'm seeing PoG reward available after 6 confirmations.

Oh you are relying on the checkmark on the UI, that is just a display bug.

Coinbases are not spendable until 102 confirms.  You can look in your "unconfirmed" balance to see all your POGs arent available.

Ill look at the checkmark bug.

2908

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

« on: December 15, 2018, 12:08:42 PM »

getblockhash is correct for me.

Keep getting this:

2018-12-15 18:03:55
 Illegal tithe @height 87725.000000, max amount 296.500000  amount 296.710000 vout 1
 Illegal tithe @height 87835.000000, max amount 296.490000  amount 296.710000 vout 2
 Illegal tithe @height 87883.000000, max amount 296.930000  amount 297.150000 vout 1 ProcessNewBlock : ACCEPTED

If a tithe is illegal, maybe one can be resent as a test and if it works send it along.

Or illegal tithe should be abandoned? It keeps showing up in the logs... is that right?  I assume it'll keep showing up because the transactions can't be abandoned currently or resent?

So on the illegal tithe, I can say with relative certainty what I "think" is happening.  (Note that Illegal Tithe and POG Pool Recipients Invalid are mostly for logging, for us to ensure we have prevented those problems in test, and then they become very rare cases of things that arent supposed to happen in prod).

I believe due to people upgrading and being on forks, the difficulty level is not exactly the same on 3 forks.  Once we all agree on the block hash, we should re-tithe, and then watch the log for one day and see that the error has dissapeared.

To answer your question though the pool will not induct an illegal tithe.  But those will be forced on their own chain anyway, so this error should dissapear once we are synced together.

(The givers actual tithe was legal on his own chain) - just illegal on our chain.

2909

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

« on: December 15, 2018, 11:56:55 AM »

Ok, Testnet seems stuck at block 87697

Im surprised so few are testing - I believe we should be able to recover because the rule was our normal rejection rule for old versions; however on a side note Im starting to dislike that rule as it really shakes up the whole system - its as if its worse to require a mandatory that way than for me to add a block version field on my logging - anyway



getblockhash 87915
f042dfcb5d9265ef681ffbe1bf3577274bcdcd13411d340a37d179ca10616810

This morning looks like we got past that does yours agree?  I have two nodes running that agree.  My 3rd is not even synced halfway let me see if I can get a third up to 87915.

2910

Archived Proposals / Re: Mass Adoption for BiblePay II

« on: December 15, 2018, 11:53:16 AM »

We will always have both,  POG will take 80% but the plan was POBH would earn 20% (block miner)

Exactly, this way solo mining pays 20% but the lions share of the pool is in-client. 

Note that I think it would be a really good idea for us to test POG in prod with POBH only (as we all agreed on so far) and write down exactly how many pool miners (in POG) we see per day - for example a pool.biblepay.org report that pulls in the exec pogpool stats in SQL so we can make a graph.  It would be very valuable to see if POG results in a daily increase in biblepay use. 

Of course we can just add pog diff to the current difficulty chart also.