BiblePay (BBP) – serves both as a decentralized autonomous charity, and as an investment. It combines many of the features of other cryptocurrencies such as Dash and Bitcoin with unique community-building features and a revolutionary approach to avoiding the irresponsible waste associated with typical heat mining. So much more than simple wealth generation, BBP endeavors to create a better world and show God’s love to others via revolutionary technology.
BiblePay utilizes a new proof-of-work algorithm based on the King James Bible, called Proof-Of-Bible-Hash (POBH). It is unique in that every miner has the entire KJV Bible integrated, making it virtually impossible to port to GPU or ASIC mining, Another key aspect of mining is Proof-OfDistributed-Computing (PODC), which is a greener alternative to traditional POW and is the primary consensus algorithm. BiblePay has built-in features that enable it to be self-funding and self-governing, based on the Dash masternode strategy, and had no ICO or pre-mine. Full accountability is built into the wallet itself – and 10% of every block can be seen to g
- The BibleHash function is fed an input X11 hash of the current block template at a point in time. This starts as a uint256. It is also fed the reference to the last block index (and previous height and previous block time).
- The BibleHash function encrypts the x11 hash uint256 using AES512 into a ciphertext vector. This ciphertext vector is then converted to base64.
- (These functions were chosen to raise the bar to reduce the likelihood of porting the hasher to a as AES512 requires the OpenSSL library).
- The resulting base64 is then md5 hashed.
- The md5 hash is 32 bytes long. The BibleHash function breaks the md5 hash into 8 octets of 4 bytes each. For each 4-byte octet, the hex is multiplied * the IVerseFactor (.4745708). This IVerse factor points to the corresponding KJV Bible verse between 0-31101. This resulting verse is chained to the output and this process repeats for octets #2-8, while appending the verses to the chained verse output.
- When the BibleHash function reaches verse #8, it breaks up the source four byte octet into four elements: a Hex 2 byte source resulting in a lookback block offset from 0-255, a hex one byte source resulting in a transaction offset of 0-15, a hex one byte source resulting in a transaction output offset of 0-15, and a one byte source resulting in a datatype pointer of 1-3 (by multiplying 0-15*.1875) (used to determine if this bible verse will need to reference a blockhash, transaction ID or a receiving address). Then the BibleHash calls out to the full node for the resulting DataType from the chain by reading the disk, retrieving the result, and appending the result to the final chained bible verse (verse #8).
- Then the resulting chained verses text contents are MD5 hashed to provide a concise input to the X11 hasher.
- The MD5 hash is X11 hashed.
- The X11 hash is sent through a business logi filter requiring the full node business logic of the latest Mandatory version of BiblePay (IE some business logic from the wallet adjusts the resulting hash depending on block number).
- Next, if the block is older than the late block threshold, the X11 hash is modified to be easier tosolve.
- If the block is a TITHE_MODULUS block, the block is easier to solve.
- The resulting X11 hash is sent out of thefunction as the hash result.