Messages

2731

Archived Proposals / Re: AirdropAlert.com - Funding Repayment (Part 3 of 3)

« on: December 12, 2018, 10:43:59 AM »

Original Post:  https://forum.biblepay.org/index.php?topic=272.0

I am requesting 444,444 BBP from the PR budget

I vote yes.

We always want to pay our owed expenses in full and have integrity.

2732

Archived Proposals / New Exchange Fund - BiblePay

« on: December 12, 2018, 10:26:55 AM »

Now that Jaap has been compensated for finishing CoinExchange.IO I would like to start a new piggy bank for our new exchange fund (Jaap is taking a break until further notice).

We have an offer to be with Cryptopia for 1.5BTC.  If nothing better comes along, this might be our best option - hopefully by December 2019.

I plan on periodically converting the latent BBP balance to BTC so as to not add liquidation risk.

I also plan on keeping records of the balance and conversion activity in our SQL server so we can see how far along we are as we go.

I am requesting 1 mil to start.

2733

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

« on: December 12, 2018, 10:11:07 AM »

i also seem to be able to select a 300 input and tithe 290. when done automatically, qt wallet wants to select a bigger input amount. is an input of 300, a legal tithe when the automated way wants mincoinvalue of 500?

So if you use coincontrol, Yes, that manual tithe would be legal.

The automated way chooses the first coin in the sorted vector that it finds that is legal that meets all the parameters, so it could be that is was in that order because of its age.  Its trying to spend the youngest aged coin that has a higher value than the diff level.

(Im testing the new version now, should be out today).

2734

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

« on: December 11, 2018, 06:08:45 PM »

in the gui, donate to foundation only allows me to select tithe amount.

in cli, exec tithe allows me to specify coin_age and coin_min_amount. I wonder if exec tithe should just allow me to specify a tithe amount only? so if I type exec tithe 300, i will either be told the tithe is legit and submit, or error out because tithe amount, coin age, or coin_min_amount is not met.

i also seem to be able to select a 300 input and tithe 290. when done automatically, qt wallet wants to select a bigger input amount. is an input of 300, a legal tithe when the automated way wants mincoinvalue of 500?

Good point.

I made a change where 'exec tithe amount' will honor the current diff level if you only specify the amount.

Regarding the min_coin_amount that is actually a bug in 1163, and is fixed in 1164 (building now).  I believe it is the source of a few issues for us.

I also removed the 2nd address you pointed out in exec pogpool.

2735

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

« on: December 11, 2018, 11:16:33 AM »

I mean that hash is somewhat random and first legal tithe is ordered by hash. Code does not select for example youngest and smallest transaction to be used for tithe.

Well just to clarify this, the only element of randomness we have is the payment tier that a giver falls into.  If a user tithes, if the tithe is legal (within diff params) it most certainly goes in the pool (when we have no bugs in our code LOL), so there is no uncertainty there - no hash - no ordering - etc.

However the payment tier your tithe ends up in is absolutely uncertain.  No once can predict what tier your tithe_weight will end up in.

Since we pay 12 blocks per 205 it should smooth it out very quickly (as far as even payments) - as long as tiers are pretty packed etc.

Ill take a look at those things in the prior post today and update asap.

2736

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

« on: December 11, 2018, 11:11:41 AM »

They are send from GUI with version 1163.
I did not see any error messages until I had no more aged coins. Until that I was able to send as many times as I wanted. I cannot recall seeing minimum diff in red.
I just reproduced this behavior and I can pump my tithes up in a very short time.

OK good to know.  So as of yesterday, I logged a couple things that could be bugs (the tithes not entering - sometimes - even though you didnt receive an error in the gui) and another one:  I believe our version of dash has a limited memory of utxo age; and I have a suspicion that some nodes are seeing a different memory utxo set - this is all really technical so what I need to do for the next version is create our own BBP map of these, so there is no chance of this "difference" and I believe this will also kill the possibility of a tithe not entering when it meets the parameters.  (On a side note I plan on adding a transaction fee to donations that increases by 1 bbp per donation - and giving that to the miner - I think this would stave off single block tithe attacks.  Although I do want to clarify to everyone, a legal tithe is a legal tithe, so dont get the idea that when one hogs a block they are doing something bad - if the coins are aged its legal - what Im trying to do is discourage it and make it financially unfeasible for someone to want to hog a single block and raise diff up for everyone at once by a massive amount).


Just to clarify on the fee:  It makes no difference what address or wallet # you tithe from, it would be like this:  Miner checks global memory pool, how many tithes on bbp network in this block?  If < 10, no extra fee to tithe.  If > 10, the tithe fee is 1 bbp for tithe #11, 2 bbp for tithe #12, ... etc.  Next block we start over at 0 again.  Also the tithing fees goes to the reaper.   The giver loses the tx fee.  This discourages tithe attacks by one "hog".

2737

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

« on: December 11, 2018, 11:07:21 AM »

I know we have a small sampling size, but this still seems odd, how are we ending up duplicating tiers so easily?

Also, i'm curious what happens when a tier is empty  the rewards just go to the miner?

"0": "Count: 0, Total: 0.0000",
  "1": "Count: 0, Total: 0.0000",
  "2": "Count: 0, Total: 0.0000",
  "3": "Count: 0, Total: 0.0000",
  "4": "Count: 0, Total: 0.0000",
  "5": "Count: 2, Total: 4054.0000",
  "6": "Count: 0, Total: 0.0000",
  "7": "Count: 0, Total: 0.0000",
  "8": "Count: 2, Total: 1450.0000",
  "9": "Count: 0, Total: 0.0000",
  "10": "Count: 0, Total: 0.0000",
  "11": "Count: 0, Total: 0.0000",
  "12": "Count: 2, Total: 3567.0000",
  "13": "Count: 1, Total: 869.0000",
  "14": "Count: 0, Total: 0.0000",
  "15": "Count: 0, Total: 0.0000",

When a tier is empty it pays 100% to the miner.  Not a problem in prod - we would easily fill up the tiers.

The clashing of tiers is not a problem; it is correct - the algorithm does not have a bug in it.

2738

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

« on: December 11, 2018, 11:05:15 AM »

In exec pogpool I see BBP address twice. Is there a reason for this?

Is nickname required? Why is it there?

Yes, the address is the Key, so it listed once as the JSON key, then the rest of the row has all kinds of things in it.  This isnt really intended for prod, as I think prod would have 500 rows of data, so this is temporary.

The nickname is optional.  Its there so you can see your tithes in testnet.  I recommend using it.

For prod we can use it for the leaderboard.

2739

Archived Proposals / Re: New Exchange Fund (recoup fronted BTC December 2018)

« on: December 11, 2018, 10:51:00 AM »

Great job Jaap, thanks for completing the coinexchange mission and for making a great web site.

2740

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

« on: December 10, 2018, 02:59:44 PM »

What happened to my donations
I sent 18*294 bbp and my pogpool says I have  294.64

Code: [Select]

{
  "Command": "pogpool",
  "ySwRWw1EEEMyGSz4iiWVAwryXbxBTumiPG": "Amount: 536.00, Weight: 1.0000, Payment_Tier: 13, Height: 85357, Address: ySwRWw1EEEMyGSz4iiWVAwryXbxBTumiPG, NickName: randrews",
  "yZVRb4Cbcoyqvw4VJmkSHPugyHxX7kbcF4": "Amount: 876.00, Weight: 0.7487, Payment_Tier: 0, Height: 85344, Address: yZVRb4Cbcoyqvw4VJmkSHPugyHxX7kbcF4, NickName: thesnat2",
  "yaSJ9FdsPcQvGjyrzxVFUPjg6wkJBQwaxc": "Amount: 1168.00, Weight: 1.0000, Payment_Tier: 10, Height: 85386, Address: yaSJ9FdsPcQvGjyrzxVFUPjg6wkJBQwaxc, NickName: thesnat1",
  "ydXPSPFWeoA9RUQoX6uBKmjnnJV6GxfwBa": "Amount: 880.00, Weight: 1.0000, Payment_Tier: 1, Height: 85297, Address: ydXPSPFWeoA9RUQoX6uBKmjnnJV6GxfwBa, NickName: jerky",
  "ygEXbdJhypUaVhYo5Q2jKATctQtVWL892K": "Amount: 1172.00, Weight: 1.0000, Payment_Tier: 11, Height: 85355, Address: ygEXbdJhypUaVhYo5Q2jKATctQtVWL892K, NickName: slybaby",
  "yhuFkP7UREXJrNrY62cBh5ZDMst7ATefCt": "Amount: 294.00, Weight: 0.2513, Payment_Tier: 0, Height: 85264, Address: yhuFkP7UREXJrNrY62cBh5ZDMst7ATefCt, NickName: testnet2",
  "0": "Count: 2, Total: 1170.0000",
  "1": "Count: 1, Total: 880.0000",
  "2": "Count: 0, Total: 0.0000",
  "3": "Count: 0, Total: 0.0000",
  "4": "Count: 0, Total: 0.0000",
  "5": "Count: 0, Total: 0.0000",
  "6": "Count: 0, Total: 0.0000",
  "7": "Count: 0, Total: 0.0000",
  "8": "Count: 0, Total: 0.0000",
  "9": "Count: 0, Total: 0.0000",
  "10": "Count: 1, Total: 1168.0000",
  "11": "Count: 1, Total: 1172.0000",
  "12": "Count: 0, Total: 0.0000",
  "13": "Count: 1, Total: 536.0000",
  "14": "Count: 0, Total: 0.0000",
  "15": "Count: 0, Total: 0.0000",
  "High Tithe": 1172.17,
  "Total Tithes": 4928.26999998,
  "My Tithes": 294.64,
  "My Payment Height": 85386
}
Here are some of the transaction ids

61836338359fa2641fb9a542d6e4bdcd242a1c505d2944ba19fc6d81074c3e1e-000
69410c348c2b6478d94f1bc0e8d0c61c6e00e613316f7628c53b78e2f1018df9-000
1bd2d45a10708ccf89a827fc12cd52f230b77a886888939cb1c1308b507062d4-000
121b947aea3282853ff90d7f79e583048d4988280ac26bf38918095207498b7a-000

So it looks like you tithed these on block 85280, and the first problem I see is txid #2, (if you look at showblock 85280 you see min diff of 1.12 age, 467 amount) and txid#2 spent a coin of amount of 98 (IE didnt meet the minimum diff req).

So that part is OK as we only induct legal tithes; but now to see if we have found a bug or not, can you please tell me - how did you tithe these on 85280, from the RPC or from the GUI?  Did the gui throw any errors and do you remember if it showed the minimum diff in red below the Send?

Also did you send from 1163?

Thanks,
Rob

2741

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

« on: December 10, 2018, 02:45:41 PM »

For simplicity sake, if we don't use coin control, the wallet will choose a balance for us that is eligible? If so, which address does it pick from first? Is it random, oldest coin age first, etc ?

Also, in our File Receiving address, I see an address for TITHES. What is that for?

Yes, wallet will choose balance eligible automatically.

It always broadcasts your tithe to be coming from the TITHES address so for rewards they come back to one place.

The TITHES address is the one it made for you for POG for the POG POOL, so your address is not changing in the POG POOL.

2742

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

« on: December 10, 2018, 02:44:32 PM »

If I understood correctly from code It picks up first eligible from map and map is ordered by hash of transaction id. So it some what random

What is it that is random?  No, all tithes count if legal tithes (within diff parameter of that block).

Nothing random, except the payment tier # you end up in.

I will answer the other questions asap.

2743

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

« on: December 10, 2018, 10:50:35 AM »

The GUI rebase is going to be hard legwork anyway so I don't really mind if we add more stuff or not. It's not going to make a huge difference.

For now I made our existing "one click mining" menu item (which already creates the biblepay.conf if it doesnt exist) check to see If Pog Enabled then:
tithing=true

(Turning on the auto tithe option)
(And this feature already sets genproclimit=1 and gen=1)

I believe they need to reboot if they do this.

2744

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

« on: December 09, 2018, 04:29:52 PM »

I think we need to work out some UI controls for tithing..

I don't believe it should be auto-on.   Though this makes for easy participation I feel the user should intentionally start this process (or risk people thinking we're a scam / stealing coins).

Klondike: i'll talk with you on IM,  I think you are expecting more than is required.

I dont really mind one way or another, but I actually thought "auto" would be the default, otherwise people will say we are intentionally trying to give the veterans more rewards.  But I see your point, I dont mind making the default =off, and we will require them to add 'tithing=auto' to the config for auto.

I did plan on thinking about a couple more controls also, like the tithe frequency.  They definiately should be able to override the default spork (which is 1 hr in testnet) by doing something like 'tithefrequency=86400' which would be equal to one day.

Let me know if you think of other controls, but we dont want to make it too complicated either. 


EDIT:

So for prod, I propose:

Default - if nothing set:
tithing=false
tithefrequency=spork_value_set_by_biblepay_devs

If a user sets them:

tithing=true
tithefrequency=Seconds_between_send


TitheCap:  Equal to 70% of our monthly POBH heat emissions (This gives miners a minimum of 30% profit on any day, and an unlimited max profit on a slow day)

Scope:  To expand POBH only for a few months, then we re-evaluate the impact this system made on bringing new users in the house. 

2745

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

« on: December 09, 2018, 01:16:59 PM »

im still dont understand whats point for this

for newbie,when we start,what i have to do?

steps.

1.step  install bbp wallet
2.step  buy bbp from exchange or ie i have 330 000bbp in wallet
3.step  whats next?

The difference is someone who buys 25000 bbp off the exchange can get started with POG almost instantly and receive mining rewards - wihtout buying expensive equipment or renting servers - their tithe total in 24 hours is the tithe_weight for the pool.  Its pretty simple to understand I think, as compared to understanding what you need to do to start PODC mining.

So the bbp miner single thread tries to send a tithe once every hour (this is a spork setting).  You can scan your log for (grep for) SendTithe.  In my case i have one exactly once per hour in the log with an error saying wallet unlock required (you need to leave your wallet unlocked in testnet if its encrypted).  I think in prod we may be able to either use the popup podc password to auto tithe.

Now do you get it?  In 24 hours all applicable tithes would be sent automatically, meaning the user is POG mining without learning anything.