Pages:
Author

Topic: BiblePay (BBP) | 10% Charity | POW/POS | CPU Only | Masternode | No Premine (Read 2358 times)

newbie
Activity: 164
Merit: 0
** BBP-Xmrig 5.10.1 - Mandatory Upgrade for Miners **


- Remove automatic tithing from the miner

* Note:  The old version of the miner tithes 10%.  Please start using the new version, as the pool now holds back the 10% orphan-tithe automatically.

Binaries:
https://wiki.biblepay.org/Upgrade_to_RandomX

** Mac is still building, MIP will notify
newbie
Activity: 164
Merit: 0
btw: some tipps for xmrig:
  • use the number of physical threads your System has, which is 12 (2x6), not 24
  • for slightly better performance enable "hugepages" in your system or start the miner as root (xmrig can configure RAM itself)
  • for even better performance you could enable "1GB-hugepages" (just google xmrig 1gb-hugepages ubuntu), but this would require a lot more RAM than you currently have (at least 40 GB)

newbie
Activity: 164
Merit: 0
Fractional sancs are now ready to test at foundation.biblepay.org.

Note that I plan on making a cool dashboard that shows a gauge of the ROI (kind of like GIN had), and the current daily ROI and stuff, but have not gotten a chance to do it yet.
But the basics should work now - and the rewards are live.  (We have one sanctuary in the farm - that I am lending to the foundation for this project, and of course we support unlimited scalability as we grow).

So here is how you test it:
- Log In
- Ensure you have a credit balance
- Navigate to Fractional Sancs
- Populate the amount you want to invest, and click Add fractional sanc.
- Wait 24 hours
- Then you should see a daily reward appear in the list, and your Foundation balance should increase.

So the main point of this is to not only let the small investor buy a fraction of a sanc and earn rewards, but also for someone on southexchange to easily create an account and a position in 5 minutes and hold it in biblepay to get the 40% ROI, etc.
newbie
Activity: 164
Merit: 0
newbie
Activity: 164
Merit: 0
** Sanctuary and Chainlocks Bulletin for block 187,000 **


Now that RandomX is stable and our difficulty has surpassed 1.0, we are planning to enable Chain Locks.  This is an exciting moment for Biblepay.

Realize that we are one of the few coins that exist that have chainlocks in Production (Other than Dash, who created it).

And, I believe we are the first Bitcoin based coin to have RandomX.  

In preparation for this, anyone who has a sanctuary, could you please ensure it is up and running?  As, once we enable Chain Locks, we move into strict mode meaning the Sanctuaries will be POSE banned and not paid if they do not respond to quorum requests.  Obviously we want to have a smooth cutover.

Lets shoot for block 187,000.


Update:

We have enabled Spork 17 (Deterministic sanctuary quorums) at block 187,000.




All Sancs seem to be up and none have PoSE score.

I wonder if there is some way to spread these great adoptions (Chainlocks and RandomX) from the PR point of view, to improve Biblepay's project exposure. I don't think there are many coins out there with this level of innovation.

Also, it would be a good hit if our exchanges know about us enabling chainlocks and reduce the number of deposit confirmations. Many investors in exchanges score coins better if they see lower confirmation numbers.
newbie
Activity: 164
Merit: 0
** BBPRIG (XMRIG) 5.10.0 - LEISURE UPGRADE **

- Merge in XMRig changes from Jan 2020 through March 2020 (MIP)
- https://github.com/biblepay/xmrig/commit/d47569b2b35802dd63f71b597af996816ca51c9a

Binaries:

https://wiki.biblepay.org/Upgrade_to_RandomX


Please test and let us know if its safe for everyone else to upgrade.  (I've unit tested it and it appears to be 1% faster).
Please also let us know if this resolves the machine language crashes for some people.


newbie
Activity: 164
Merit: 0
Where do people download the bbp xmrig software again?

https://github.com/biblepay/xmrig/tree/master/binaries

Is this the best location?

Yeah normally i just download directly from github, all about your taste i guess. Directly from pool page also a option.

I am using port 3001 on rx.biblepay.org - the block height says 2062258

Height should be 184675. Am I mining on the correct chain? That block height looks awfully high, like it is testnet chain or something...

I haven't tried xmrig in a long time, so I could be mistaken too.

https://i.imgur.com/tDIR32B.jpg

As we covered in testnet we display the randomX height there and when you solve BBP shares then we pass through BBP height and bbp diff.

So that part is A-OK.
newbie
Activity: 164
Merit: 0
newbie
Activity: 164
Merit: 0
*** NEW RANDOMX GIVEAWAY FOR NEW RANDOMX USERS ***
https://forum.biblepay.org/index.php?topic=503.msg7138#msg7138
Feel free to promote.  I believe we can do this for the first 150 new RX miners.

https://wiki.biblepay.org/Upgrade_to_RandomX

from:
https://forum.biblepay.org/index.php?topic=490.msg7143#msg7143

** Solution if your miner crashes when mining randomX **
Create a batch file on windows with the following
Code: [Select]
:miningloop
xmrig.exe -o rx.biblepay.org:3001 -u bbpaddress -p moneroaddress --threads=8
goto miningloop
newbie
Activity: 164
Merit: 0
BiblePay - 1.5.0.7
Mandatory Upgrade for Entire Network @184675 (March 24th, 2020)

- Add RandomX Mining to biblepaycore
- Add corporate whitebranding (for the future - this is dormant)
- Add DAC images and logos
- Merge Dash Mainnet changes up to Jan 2020 into Prod mandatory release
- RandomX starts at 184675
- Merge in changes to block database
- Move datastore to ~/.biblepay

** Note: This upgrade also requires new mining software after block 184675, with the switch to RandomX
** Note:  The wallet and data directory have been moved back to our original location (~/.biblepay) to cut down on confusion.  
** Our github location has been moved back to the original location (https://github.com/biblepay/biblepay)
** The new RandomX pool will come on-line approx. 1 day before our go live.  The address will be:  rx.biblepay.org
** Binaries have been released, and names and sha hash names have changed on biblepay.org.  Note, I believe we will not be able to release binaries for Rasberry pi or Arch.  You may be able to self compile those.  We are also limited to initially releasing 64 bit binaries for Windows and Linux.  (NOTE:  This is not because we are lazy or don't care about 32 bit, it's because both MIP and I receive errors in the randomx compile process for the 32bit processors.  We believe RX may not work on 32bit, therefore we must delay 32bit until we do more research.)  Please provide feedback to us if you find a binary is missing or does not work.

Please see this document for upgrade instructions:
https://wiki.biblepay.org/Upgrade_to_RandomX

newbie
Activity: 164
Merit: 0
Quick question about the CPK.  As I get more funds into my BBP wallet, do I have to occasionally send more funds to my CPK for them to be counted towards my coin age?  Thanks!

Coin-age is required only if you are doing PoDC (Boinc). I assume you are doing that; so you are correct, only funds in the CPK address count towards PoDC coin-age.

Having said that, there is no reason to keep increasing your coins in the CPK address unless you are running short on collateral for PoDC (i.e., increasing RAC).
newbie
Activity: 164
Merit: 0
DWS (Dynamic Whale Staking)

https://i.imgur.com/OCz1Q7E.png

Potentially gain 40% interest on your coins right now by staking them for one year

With mining, I have to make sure the miners stay updated and are running 24/7, I have to pay for electricity

Similar with a masternode, it has to stay updated and run 24/7, and I have to pay for a server

Staking, you just burn it!

https://wiki.biblepay.org/DWS_Setup
newbie
Activity: 164
Merit: 0

MIP whats cmd for upgrade linux, forgot it, thanks...... good to add on main web in tutorials, missing it there

Using the masternode script
./masternode-install.sh -u -n

Manually
wget https://biblepay.org/biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
tar -xzf biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
#stop daemon, move/copy binaries to replace older, restart daemon


thanks.... appreciate it....thx to orbis with help how to setup this MIPs packages

I use this:

Code:
biblepay-cli stop
sleep 30
cd /usr/local/bin
sleep 5
rm biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3
wget https://biblepay.org/biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3
tar xvf biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3
rm biblepayd-evo-x86_64-pc-linux-gnu.tar.gz
sleep 3


biblepayd --version
sleep 3
biblepayd --daemon
sleep 3
cd ~
sleep 1
cd .biblepayevolution
sleep 1
tail -f debug.log

For biblepay miner:

Code:
cd .biblepayevolution
pkill bbpminer_linux
rm bbpminer_linux
rm bbpminer_linux
wget https://github.com/biblepay/cpuminer/raw/master/binaries/bbpminer_linux
chmod 755 bbpminer_linux
newbie
Activity: 164
Merit: 0
New wallet is crashing. Installed on previous version.
Error was 2020-01-20 16:06:52 ERROR: ReadBlockFromDisk: Deserialize or I/O error - ReadCompactSize(): size too large: iostream error at CBlockDiskPos(nFile=0, nPos=11296509)
I deleted my blocks directory to force rescan, now is crashing with no error in log.
Have you tried restarting with the "-erasechain=1" switch?
newbie
Activity: 164
Merit: 0
BiblePay
1.4.8.6-Mandatory Upgrade for Entire Network @ 170830

- Increase sanctuary protoversion to 70751 (Enable new consensus rules
for PODC - fix low payment bug)
- Adjust deflation rate to match target in GetBlockSubsidy
- Add anti-gpu measures to POBH (reject high-nonce blocks)
- Mandatory height: 170830
- Adjust DWS creation and validation for DWS 2.0
- Add upgradesanc warning when no \r\n exists (Togo)
- Add addl warnings to exec rac, and ensure exec rac does not crash the
node
- Remove dead code from miner; modify miner to handle anti-gpu nonce
rules

** Note: We also have a mandatory upgrade for the external miner, please find the binaries here:
https://github.com/biblepay/cpuminer/tree/master/binaries

** Sanctuaries, please upgrade also

** The new POBH 2.0 rules do not start until 170830, so in the mean time, the pool will reject most of the shares.  As soon as this height passes the pool should start working correctly.  The pool is coming back online now.

POOLS:  Please upgrade.  The software has been updated here:
https://github.com/biblepay/node-stratum-pool/commits/master
To upgrade please follow the upgrade instructions in this document:
https://github.com/biblepay/node-open-mining-portal/blob/master/Deploy%20a%20Nomp%20BiblePay%20Pool.txt
Pages:
Jump to: