Bible Pay

Read 303352 times

  • sunk818
  • Global Moderator

    • 521


    • 36
    • April 24, 2018, 02:02:20 PM
    more

Is MINEXMR giving you that message? It doesn't like the BBP miner?

Hey Rob.

Was checking log for dual miner and i get these messages:

Code: [Select]
[2020-05-22 17:23:57.015] speed 10s/60s/15m 16463.3 16449.0 16445.0 H/s max 19799.5 H/s
[2020-05-22 17:24:07.563]  cpu  rejected (3045/101) diff 354926 [676403] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (303 ms)
[2020-05-22 17:24:07.934]  cpu  rejected (3045/102) diff 354926 [507614] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (285 ms)

And i noticed the  xmr charity adress  also  looks like the hashrate over there  is way to low. 
Hmm any ideas?
[/quote]
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • sunk818
  • Global Moderator

    • 521


    • 36
    • April 24, 2018, 02:02:20 PM
    more
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
New article: https://www.bitrates.com/news/p/biblepay-a-cryptocurrency-for-christian-charity-and-activism

Thanks- thats a really nice article.

One thing I like about it is Mike Dalton seems to understand what we are trying to do.  He shows that our payments to our vendors are legitimate and we operate with integrity.
He explains the breakdown of our expenses.  This is what we need - more people who believe in us and our future.

I really need to focus on writing a two page update on where we are today - that explains the new idea of leveraging randomx liquidations for charity - and not driving our price down, and a summary of what makes us special compared to other coins (as a lot has changed in the last year) and I know we can appear confusing to the general public with all this high-tech info.



  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Hey Rob.

Was checking log for dual miner and i get these messages:

Code: [Select]
[2020-05-22 17:23:57.015] speed 10s/60s/15m 16463.3 16449.0 16445.0 H/s max 19799.5 H/s
[2020-05-22 17:24:07.563]  cpu  rejected (3045/101) diff 354926 [676403] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (303 ms)
[2020-05-22 17:24:07.934]  cpu  rejected (3045/102) diff 354926 [507614] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (285 ms)
[2020-05-22 17:24:33.225]  net  new job from foundation.biblepay.org diff 345365 algo rx/0 height 2103950
[2020-05-22 17:24:48.879]  cpu  accepted (3046/102) diff 7 [7] BBP (357 ms)
[2020-05-22 17:24:57.038] speed 10s/60s/15m 16451.8 16438.6 16444.4 H/s max 19799.5 H/s
[2020-05-22 17:24:57.384]  cpu  rejected (3046/103) diff 345365 [639672] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1452 ms)
[2020-05-22 17:25:45.563]  cpu  rejected (3046/104) diff 345365 [804752] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (293 ms)
[2020-05-22 17:25:57.068] speed 10s/60s/15m 16464.1 16455.0 16444.4 H/s max 19799.5 H/s
[2020-05-22 17:26:07.069]  cpu  rejected (3046/105) diff 345365 [465059] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1670 ms)
[2020-05-22 17:26:46.113]  cpu  rejected (3046/106) diff 345365 [583328] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (287 ms)
[2020-05-22 17:26:57.092] speed 10s/60s/15m 16460.7 16454.4 16444.6 H/s max 19799.5 H/s
[2020-05-22 17:27:14.116]  net  new job from foundation.biblepay.org diff 330509 algo rx/0 height 2103950
[2020-05-22 17:27:31.473]  cpu  rejected (3046/107) diff 330509 [2146629] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (295 ms)
[2020-05-22 17:27:57.120] speed 10s/60s/15m 16463.3 16454.3 16444.6 H/s max 19799.5 H/s
[2020-05-22 17:28:14.907]  cpu  rejected (3046/108) diff 6 [27] BBP "Stale" (292 ms)
[2020-05-22 17:28:16.925]  cpu  rejected (3046/109) diff 6 [22] BBP "Stale" (311 ms)
[2020-05-22 17:28:19.913]  cpu  rejected (3046/110) diff 6 [186] BBP "Stale" (299 ms)
[2020-05-22 17:28:25.893]  cpu  rejected (3046/111) diff 330509 [364286] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (295 ms)
[2020-05-22 17:28:33.918]  cpu  rejected (3046/112) diff 6 [8] BBP "Stale" (297 ms)
[2020-05-22 17:28:46.931]  cpu  rejected (3046/113) diff 6 [15] BBP "Stale" (304 ms)
[2020-05-22 17:28:48.915]  cpu  rejected (3046/114) diff 6 [8] BBP "Stale" (288 ms)
[2020-05-22 17:28:50.035]  cpu  rejected (3046/115) diff 330509 [359717] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (586 ms)
[2020-05-22 17:28:52.079]  net  new job from foundation.biblepay.org diff 322178 algo rx/0 height 2103951
[2020-05-22 17:28:55.187]  cpu  rejected (3046/116) diff 322178 [1307535] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (275 ms)
[2020-05-22 17:28:57.140] speed 10s/60s/15m 16446.7 16424.6 16445.7 H/s max 19799.5 H/s
[2020-05-22 17:29:03.916]  cpu  rejected (3046/117) diff 1 [1] BBP "Stale" (284 ms)
[2020-05-22 17:29:14.007]  cpu  rejected (3046/118) diff 322178 [330347] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1457 ms)
[2020-05-22 17:29:16.881]  cpu  rejected (3046/119) diff 322178 [2403792] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (1176 ms)
[2020-05-22 17:29:20.941]  cpu  accepted (3047/119) diff 1 [1] BBP (299 ms)
[2020-05-22 17:29:23.918]  cpu  accepted (3048/119) diff 1 [1] BBP (277 ms)
[2020-05-22 17:29:25.061]  cpu  accepted (3049/119) diff 1 [1] BBP (420 ms)
[2020-05-22 17:29:32.245]  net  new job from foundation.biblepay.org diff 316878 algo rx/0 height 2103952
[2020-05-22 17:29:34.912]  cpu  accepted (3050/119) diff 2 [4] BBP (266 ms)
[2020-05-22 17:29:37.935]  cpu  accepted (3051/119) diff 2 [4] BBP (287 ms)
[2020-05-22 17:29:50.829]  net  new job from foundation.biblepay.org diff 316878 algo rx/0 height 2103953
[2020-05-22 17:29:57.163] speed 10s/60s/15m 16448.4 16441.2 16445.8 H/s max 19799.5 H/s
[2020-05-22 17:29:58.939]  cpu  accepted (3052/119) diff 4 [5] BBP (284 ms)
[2020-05-22 17:30:04.954]  cpu  accepted (3053/119) diff 4 [136] BBP (294 ms)
[2020-05-22 17:30:06.068]  cpu  accepted (3054/119) diff 4 [136] BBP (409 ms)
[2020-05-22 17:30:18.792]  net  new job from foundation.biblepay.org diff 314281 algo rx/0 height 2103953
[2020-05-22 17:30:24.790]  cpu  rejected (3054/120) diff 314281 [335514] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (293 ms)
[2020-05-22 17:30:47.360]  cpu  rejected (3054/121) diff 314281 [397291] XMR "UPDATE YOUR MINER your IP is temporarily blocked for 10 mins" (288 ms)
[2020-05-22 17:30:48.739]  net  new job from foundation.biblepay.org diff 311726 algo rx/0 height 2103954
[2020-05-22 17:30:57.187] speed 10s/60s/15m 16453.1 16445.0 16445.5 H/s max 19799.5 H/s

And i noticed the  xmr charity adress  also  looks like the hashrate over there  is way to low. 
Hmm any ideas?

So although I posted a warning last month that we were warned once from MineXMR about our traffic setup from foundation.biblepay.org, I got ahold of them, and explained what we are trying to do and they whitelisted us that we will be in good standing with up to 1,000 pool connections.  And, of course we are also working on standard merge-mining for our June release so that we dont have a specific risk (IE if minexmr goes down we go down), so that is happening too.

That being said, foundation is not issuing that message- it appears to come from MineXMR for your IP, but whats strange is I havent received one other complaint and you would think this would be an issue with more than one user (unless your IP sent some very strange things recently) - Or, if Xmrig made an emergency change in the last 24 hours.

Let me fire up my XMR miner and see if I can reproduce.

Anyone else experieincing any problems on foundation.biblepay.org with RX mining?

EDIT2:  Charity hashrate is OK - we recently moved to 24 hour assessment to make it a little more exact - so because of the big lump during 2 hours, the other 22 hours make it 16KHS which is right for the miniscule amount foundation is handling right now (bbp.miningpool.fun is doing 2/3rds of the hash rate today).

EDIT3:  In the mean time can you also try "bbp.miningpool.fun" to see if its isolated to foundation?  Ill test mining next.

EDIT4:  Im mining OK against foundation.

« Last Edit: May 23, 2020, 04:28:55 PM by Rob Andrews »


  • Costa82
  • Newbie

    • 24


    • 5
    • April 23, 2020, 09:10:05 PM
    more


Anyone else experieincing any problems on foundation.biblepay.org with RX mining?



i experienced a similar problem yesterday although i dont have the screenshot.
"Update your miner, your ip will be banned for 10 minutes"  or something along this line


  • earlzmoade
  • Super Developer

    • 311


    • 48
    • August 02, 2018, 03:22:01 AM
    more
It looks fine for me now, seems it was just during 22 may i was getting that miner ip block thing....
Nor do i have botnet with computers or such, i got 8 rigs running..

I guess just mineXMR doing something..

Quote
And, of course we are also working on standard merge-mining for our June release so that we dont have a specific risk (IE if minexmr goes down we go down), so that is happening too.

Sounds awesome!  Keep up the nice work!  ;D
Joshua 1:9
Have i not commanded you?
Be strong and courageous. Do not be afraid;
do not be discouraged, for the Lord your God
will be with you wherever you go.


  • sunk818
  • Global Moderator

    • 521


    • 36
    • April 24, 2018, 02:02:20 PM
    more
https://github.com/biblepay/biblepay/commit/bedfb82a3271b42e208584b5ddf00b6063a9806d


Rob, Thank you for the impressive set of updates! My apologies for not being more involved. This pandemic has really affected me in a negative way.


Do you know if we can see what the RAC to BBP payout ratio will be with 1.5.1.4? If not, its okay. I just thought it'd be nice to chart out RandomX payments with PoDC payments. (I was thinking either in exec price, or exec rac seeing this information is helpful). I've been looking at Google Data Studio to build dashboard via Google Sheets, but so far I've keeping the Google Sheets charts up to date.


Anyway, with the proposed changes of POOM going to RandomX, I think the PoDC payout for computing power will reach a nice equilibrium. Also, the DWS changes will give stronger incentive to burn BBP as opposed to the sanctuary. So, all in all, I think you've done a great job balancing out all the economic incentives.
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
https://github.com/biblepay/biblepay/commit/bedfb82a3271b42e208584b5ddf00b6063a9806d


Rob, Thank you for the impressive set of updates! My apologies for not being more involved. This pandemic has really affected me in a negative way.


Do you know if we can see what the RAC to BBP payout ratio will be with 1.5.1.4? If not, its okay. I just thought it'd be nice to chart out RandomX payments with PoDC payments. (I was thinking either in exec price, or exec rac seeing this information is helpful). I've been looking at Google Data Studio to build dashboard via Google Sheets, but so far I've keeping the Google Sheets charts up to date.


Anyway, with the proposed changes of POOM going to RandomX, I think the PoDC payout for computing power will reach a nice equilibrium. Also, the DWS changes will give stronger incentive to burn BBP as opposed to the sanctuary. So, all in all, I think you've done a great job balancing out all the economic incentives.

Thanks Sun!


On the Rac->BBP Payment ratio, its not programmed yet, but, I just added it to my todo list, and we can do it as a leisure.  Ill try to see if we can get to that soon.  Im also trying to release a design for unchained so we can keep working on that.

« Last Edit: May 25, 2020, 01:38:13 PM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
BiblePay - 1.5.1.4
Mandatory Upgrade



Height 199,000
Date: June 2nd, 2020
https://github.com/biblepay/biblepay/releases/tag/1.5.1.4


- Add BBP unchained (1000 Transactions per second support) core wallet
support
- Add RX merge-mining (allows usage of the XMRig miner and changes our
pool protocol to be more compatible).  Merge mining starts at height
199,000 and requires a miner upgrade and a pool upgrade.
- Add queued proposals (allows the user to add more than one pending
governance proposal)
- Add Russian and Ukrainian bible translations (Marcus Antonio)
To see the Russian, Chinese, and Ukrainian bibles, from QT click BIBLE
from the top horiz menu and change the language.  To read a verse in
Russian from the console type: exec readverse CO2 10 RU
- Retire POOM (Remove listchildren, get poom payments).
Cancelsponsorship still works to allow you to remove children.  Remove
the POOM budget making it available for RX heat mined rewards.
- Fix alerts to allow devs to send an alert (this just shows a mission
critical status bar message on the top of the core wallet)
- Add XMR price to 'exec price'
- Ensure exec revivesanc uses the CPK as a source of funding (this keeps
it from failing).  Revivesanc lets you revive your sanctuary if its been
pose banned.
- Added the percentage arg to gobject vote-many (lets you utilize a
percentage of your sanctuaries in a vote)
- Add sanctuary spork voting; this allows Sanctuaries to vote in a spork
value EDIT or ADD.  This basically allows the sancs to control the
vendor list and the pool list (and other functionality).
- Remove 'evolution' from QT installer
- Fix LLMQ params so that ChainLocks will POSE ban nodes @200,000
- Increase DWS budget by double (per sanc vote
https://forum.biblepay.org/index.php?topic=532.0) and increase deflation
rate to pay for this change.



  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Does anyone have any really good idea on how we could make BiblePay go viral by adding in some type of referral code or reward system?
For example I see on HEX, they have some type of lead generation where a referral code given to another person causes them to get a reward of a higher % when they invest in HEX, but, I dont really understand it or have the details on that.

If you have any good ideas (including modifying our algorithm with stipends or subsidies) to make biblepay go viral, please share them.  And when you do, please include an actual working example with details (not just something vague) so I can evaluate it and talk more about it.

Or if you think its a bad idea tell us why its bad also.



  • togoshigekata
  • Hero Member

    • 527


    • 31
    • September 01, 2017, 10:21:10 AM
    • USA
    more
I think this is how HEX works

=

There are 3 ways to get HEX tokens:

1. You sign Bitcoin addresses (proving you own Bitcoin) and enter it into the smart contract

2. You give Ethereum to the smart contract

3. You buy on exchanges

=

Smart contract UI:  https://go.hex.win/

=

So how does the referral system work?

You install an Ethereum wallet and generate an Ethereum address

Then you add your address as a parameter to the hex website link

https://hex.win/?r=YourETHaddress

Then you get people to click it, and when they do, it puts a cookie on their computer with your address

and then when the person goes to get HEX tokens
by doing 1 or 2 above (signing BTC or giving ETH) with the smart contract UI

you get a 20% bonus of that HEX and they get a 10% bonus of HEX

=

Read Contract and Write Contract:
https://etherscan.io/token/0x2b591e99afe9f32eaa6214f7b7629768c40eeb39

(I see a "referrerAddr" field for the btcAddressClaim and xfLobbyEnter functions)

Contract Code:
https://etherscan.io/address/0x2b591e99afe9f32eaa6214f7b7629768c40eeb39#code

====

BiblePay could do a UTXO snapshot/claim/sign thing, I think you've talked about potentially doing this for DASH coin

And something interesting HEX did as a twist, they made 90% of the free coins from claiming/signing BTC, automatically stake for 365 days, so that people couldnt immediately dump their free HEX coins on the market

=

So on the "giving ethereum" thing, I believe Richard is getting all that money directly, he never says who owns it, never promises anything, never talks about the money, and says to have no expectations

I dont understand the legal stuff,
here is the disclaimer:
https://hex.win/disclaimer.html

=

NOTE: Richard Heart may own 50% of HEX
https://medium.com/@TooWumboToFail/under-a-hex-396847b86e57

=

Hope this helps!


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
BIBLEPAY HAS BEEN LISTED ON VINDAX










Vindax looks very promising for us; based in Vietnam, accepting US customers, they are 18* bigger than Tokok, doing 18Mil per day adjusted volume on coingecko:

https://www.coingecko.com/en/exchanges/vindax

(This is close to half the size of Bittrex volume) and they have 25K twitter followers.


The ETA to start trading is sometime later today (May 27th 2020, in approx ~4 hours).  They have already upgraded to our June mandatory. 


URL:


https://vindax.com/



One nice thing about Vindax:  They are working on a decentralized exchange- we should have no problems being automatically listed there in the future.  The current exchange is centralized.




  • sunk818
  • Global Moderator

    • 521


    • 36
    • April 24, 2018, 02:02:20 PM
    more
Does anyone have any really good idea on how we could make BiblePay go viral by adding in some type of referral code or reward system?


You have the faucet code that generates for the wallet. Maybe you can do something similar where you can do a DWS burn but add a one-time wallet code that is funded and pays out as a bonus after 1 year. Maybe there will be tiers of bonus percentage based on how much you burn for a year?


1% for 10k
5% for 100k
10% for 1M
BH6oxjLkyz3z8FYpvU3ZR7PTZ31Xt9DkXZ


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more

You have the faucet code that generates for the wallet. Maybe you can do something similar where you can do a DWS burn but add a one-time wallet code that is funded and pays out as a bonus after 1 year. Maybe there will be tiers of bonus percentage based on how much you burn for a year?


1% for 10k
5% for 100k
10% for 1M

Thats a pretty good starting point, because it covers two important aspects of viral:  Since the coins are getting burned, they have no choice but to buy them first (or burn existing coins).  In contrast to rewards for "buying coins off of SX first with a referral code" (as that could be gamed).  I also like the lockup duration idea, because that keeps them locked for a year.

So to continue on this we also need to make it viral.  Something that entices a user to share this with another user and get a reward maybe.  Once word of mouth picks up like that I think then the outcome is more like HEX (free advertising).  How could we do the referral codes and rewards....

If we e-mailed any existing DWS burn candidate an existing burn TXID, I wonder if that TXID could be the referral code for another future burn by someone else.
So in your example above, you get the DWS standard quoted reward if you do a normal burn in the console, but, if you use a "prior burn TXID" you get the bonus % you mention above....

That might work virally:



EDIT II:

So to summarize System A (Bonus Rewards for Burning coins) vs System B (Viral Bonus Rewards for Burning Coins):

In System A, anyone that finds out about BiblePay can receive a 10% bonus if they burn 1MM coins for a year.  This limits the exposure to how many people find out about biblepay naturally or through our PR efforts.

In System B, a user can not only receive the standard DWS burn % + a full 10% bonus, but can also receive an addl 3% referrer reward for sending a referral code to a friend, who ultimately provably creates a new burn (then the new friend gets the 10% bonus, the original user gets the 3% referral bonus). 

Bob:  1MM burn (receives 10% + a TXID)
Bob signs the TXID by typing 'referfriend'
Jon receives the referral code, and burns 1MM (Jon receives 10% on the 1Mil, in this tx at expiration an addl 3% goes back to Bob).
Jon is free to generate a new referral code on his burn also.
(We also should consider if Jon can create more than one referral code, I think we should not limit it - let it be unlimited).


Imho, the viral idea seems pretty good on the surface, as compared to plain vanilla whale stakes?

EDIT III:

I was thinking how to simplify this further and I think all we really need is an additional function to make DWS (dynamic whale stakes) viral:

getreferralcode would generate a referral code from ones wallet using their CPK as the receiving address for the bonus reward plus the referral code.
So basically, anyone can make referral codes and share them with anyone.    IF they are used by another person, that whale stake will have an integrated payout mechanism that would kick back 3% to the referer automatically (as it could decode the CPK out of the referral code automatically).


« Last Edit: May 27, 2020, 10:50:53 PM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 4097


    • 97
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
BIBLEPAY HAS BEEN LISTED ON VINDAX










Vindax looks very promising for us; based in Vietnam, accepting US customers, they are 18* bigger than Tokok, doing 18Mil per day adjusted volume on coingecko:

https://www.coingecko.com/en/exchanges/vindax

(This is close to half the size of Bittrex volume) and they have 25K twitter followers.


The ETA to start trading is sometime later today (May 27th 2020, in approx ~4 hours).  They have already upgraded to our June mandatory. 


URL:


https://vindax.com/



One nice thing about Vindax:  They are working on a decentralized exchange- we should have no problems being automatically listed there in the future.  The current exchange is centralized.

I opened ticket #877946 to see why we are in maintenance still.

(I can see the wallet available in the Funds list, but its in maintenance). 

Today, the exchange is in maintenance.

(I'm actively monitoring the situation).  I've emailed Michelle back and forth, and the tech support during the integration, so I do not believe we were scammed in any way.
I feel if anything, something happened behind the scenes at the exchange and they are trying to resolve it...



« Last Edit: May 30, 2020, 12:53:19 PM by Rob Andrews »