Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Rob Andrews

Pages: [1] 2 3 4 5 6 7 8 ... 11

Active Discussions / BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: January 06, 2025, 01:08:46 PM »

This is our TestNet thread for our new BBP - DOGE Decentralized Exchange!

Welcome!

Please sign up here if you can help us test the feature.

Wallet download:

https://biblepay.org/wallet

Or

Self Build: https://github.com/biblepay/biblepay/commit/2ba1eb9386960e0749f1cab64414019cc2502fea

Or

Direct link to win64:
https://biblepay.org/biblepay-win64.exe

Active Discussions / June 2024 (Q2) - Babylon Falling Release

« on: April 30, 2024, 07:32:54 PM »

June 2024 Release - Babylon Falling

Welcome to TestNet - Babylon Falling!

Testing Starts: May 4th, 2024
Testing Ends: June 4th, 2024

In this thread we will be testing:

- Ability to create a sanctuary of each size (Altar, Sanctuary, Temple) with collateral amounts (455,001, 4,500,001, and 45,000,001) and corresponding payments of (10%, 100%, 1000%)
a. Verify each size of sanc can register properly and appear in the deterministic masternode list
b. Verify the payment amount on each sanc
c. Verify the chain can sync from 0 after we solve some temple blocks
- Verify the monthly superblock still works and emits and is the correct amount
- Verify Quorums form
- Verify Temple and Altar coins in wallet lock in coin control and require an unlock (like regular sancs) so they dont get spent by accident
- Verify inactive sanctuaries (IE investor nodes) receive 50%
- Verify masternodelist shows the Tribe for a Temple
- Cutover height ________195350_________________________
- Block hash :
getblockhash 195350
00001a40008c45546bbc725caf32e5238bfdd70eca982c0d220c0f92542dfb9c

Explain Changes to Entire BiblePay Network:

- Explanation :

___________________________

Wiki Articles:

Older - Create a Sanc:
https://wiki.biblepay.org/Create_Sanctuary

Starting Version: 0.20.3:

(Please ensure your version is greater than this, in order to sync. See post #2 for current hash.

Testnet Download Links:

Ready:

Windows 64-bit: https://biblepay.org/biblepay64develop.exe
Linux : Self compiled version ready (please post if you want Ubuntu binary)

NOT READY (ask before trying):
(Inquire first before downloading)
MacOS QT: https://biblepay.org/biblepay-harvest-develop.dmg

Linux 64 bits (QT/biblepayd/biblepay-cli) zip: https://biblepay.org/bbp-lin-develop-64.zip

To self compile:
git pull origin develop

https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt

CONFIGURING FOR TESTNET:

Create a biblepaytest.conf file with the following contents:
testnet=1

Place the file in ~/.biblepaycore

Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepaycore/testnet3 folder.

NOTE: If you only have one machine, you can run in testnet side by side a prod node.

To create a TestNet Sanctuary:

https://wiki.biblepay.org/Create_Sanctuary

__________________________________________________________________________________________________________________________________________________________________________________________

OUR BIBLEPAY CORE TESTERS

#1 -

#2 - Mr. A

#3 - Rob Andrews

#4 -

Active Discussions / Unchained Web - v1.37 - Red Sea Parting Release - Q1 2024

« on: February 20, 2024, 09:06:55 PM »

Good evening and God bless everyone.

Before going into the new site, let me review some of our older web solutions:

First we had the BBP Foundation web site, which was simply a Microsoft site that used a conventional centralized database and allowed users to watch God videos, do fractional sanctuary staking, post twitter like alerts and had some gospel features.

Then we had BMS 1.0, where we had node-to-node (server) communication with an independent sidechain but it was limited in that it was not fully synchronized with the core wallet and it didn't have a very good UI layer.

Then we had Unchained.biblepay.org v7.1, which was an MVC solution, and finally did integrate with a cockroachdb cluster, had a non synchronized sidechain, could send money independent of bbp core wallet, had an API, and offered videos stored on BBP-wrapped-storj, and even hosted the BBP softphone. Although "warm", I was still looking for BBP to have a true synchronized and immutable sidechain offering, hence the reason for the rewrite. I also discovered that the in-wallet version of Unchained received very little interest since we could not make phone calls without launching the core wallet (it would be much more useful to make a call from a web page).

Now we have Unchained-RedSeaParting v1.37 that is being released. It is our MVP (minimal viable product release) of unchained. Meaning that this time, features do not exist in it that are not fully finished; they are held back.

This version attempts to "fix" all of the shortcomings in prior versions technologically speaking as each foundation has a pro and con. I have a plan to bridge permissions, business objects, the sidechain and the UI in a way that binds those fields to new pages in such a way as to make BBP a unique solution for certain apps. So when you are reviewing the UI you may think that it oddly feels like Windows, but that is by design. To give an example of what the vision is in the future, imagine this:
Rob owns XYZ corp, and grants (on chain) permissions to RWAD for two business object tables : property and lease to his BBP coworkers Alice and Bob. Bob grants R to John.
Then Bob creates a new page for viewing Lease and Adding Lease with 10 new fields. Each of these coworkers will be able to RWAD or R these pages respectively, all on chain. Hence the reason for the look and feel of "an app" and windows.

First, if you are coming from Unchained and you have an NFT or a balance, you can log in to this new version by pasting your private key as your password, and using your email address as your username.

You can get your private key by finding your "Unchained" address in your core wallet, and typing "dumpprivkey your_unchained_address". Once you are logged in you may change your password and hit Save.

Alternatively if you dont care about your old account you can Register as a new User.

Some things I would like to discuss:

Highlights of the new system
Things we Achieved (completed)
Things that are ToDo, and an updated roadmap
The Vision

TODO:

- Create a Responsive view for mobile devices. Right now the pages work on mobile, but they require you to pinch and squeeze.
- Linked immutable sidechain needs finished
- Permissions and Grants
- App sections backed by secured role views
- Sending a Note with a TX in the core wallet, and having the receiver read the note that is generated by the sidechain Inside the core wallet (demo hybrid integrated functionality)

Completed Items:

Note: The phone system now works from mobile phones as of today!
[Add Completed Items Here]

Vision:

- Permisionless Zero Trust security architecture (this means even the devs cannot break the security of the sidechain. Granted permissions are virtually impossible to hack-except by breaking a full key, even by the creator).
- Blocks are immutable and linked to the sidechain blocks in a forward only fashion. Nothing can be squeezed in between or rolled back, therefore they are immutable and secure.
- Temples provide the database security for our Cockroachdb cluster; with each temple required to run one cockroachdb node in the future (current state we run 3 from the first 3 temples to bootstrap the project until it is stable)
- Cockroach automatically "fills in the gaps" on unsynchronized content, which is very exciting. This means we scale. And we scale automatically.
For example, if 3/4 nodes are synced, and one new temple comes online, it will automatically sync or fill in the entire sidechain without any BBP code.
Cockroach also streams content in parallel, so when you request a report it is fulfilled by many nodes.
- The forward only sidechain block index has corresponding database Views that represent table objects for user consumption.
These always maintain their integrity since even if one was altered or corrupted, it would regenerate from the cluster, which is based on the forward only sidechain transactions that
drive the view. No user can alter the sidechain content, except by paying for transactions that go in it.
Transactions look like this:
BBP Core TX -> Contains Metadata
Sidechain TX -> Contains 1:many transactions that occur within one BBP block.
Each sidechain tx can alter a Business object, or can point to media (such as a video or a file).
Thousands of sidechain tx's can fit in one metadata tx that is secured by one BBP block.
The sidechain tx's are instantsend locked.
Sidechain transactions are almost instant because they run at the speed of our cluster.
Storage on the sidechain is cheap, and extremely cheap to use our sidechain to store videos or files, as we store the actual video or file on storj, and our sidechain stores the pointer to that data.
- Binding a new page to BBP objects will be simple once the foundation is released
- We have a new secure API. You can access certain API endpoints and functions with the BBP keypair.
Other endpoints require a temple (such as interacting in debug mode in prod from a hosted satellite).
- Field captions in our dictionary and language literals
- A temple is required to Host an unchained web satellite instance
By requiring a temple signing key for every cockroachdb write, we can securely maintain the integrity of every zero trust object in the view.
For example, if I own NFT 123, and I sell that NFT to user B, that sidechain transaction will only "transfer" via a hosted tx that executes on a web node owned by a Temple and that
temple signs the tx. This way, even our devs who debug the code cannot facilitate transactions in prod unless they debug from a temple, however we will have a Full testnet so that debugging is not a problem.
- Sanctuary voting for upcoming features

Let me know if anyone has any trouble signing in or testing.

Current state, unchained is meant to run on a desktop until we have bandwidth to tackle the Responsive Mobile endeavor.

Production Proposals / Feb 2024 orphan expenses cameroon-one

« on: January 27, 2024, 07:07:18 AM »

We currently sponsor 5 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 7MM bbp (approx $250) covering a high proportion of the orphans (we pay $40 per month for each orphan) and we still have an outstanding balance owed to Cameroon-one ~$500 for the last month of 35 orphans as of Jan 2024.

Payout going directly to cameroon-one: BHxAQBE9YfZNW2Cwv9jqQ9KQn8nxdbm9Z9
** Note, this is now Todd F's Bololex address, as SX went out of business, please keep on file for future **

Production Proposals / Jan 2024 Orphan Expenses - Cameroon-One

« on: December 23, 2023, 07:59:40 AM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 7MM bbp (approx $500) covering a high proportion of the orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Production Proposals / Dec 2023 cameroon-one expenses

« on: November 23, 2023, 12:04:43 PM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 7MM bbp (approx $540) covering a high proportion of the orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Production Proposals / Nov 2023 Cameroon One Orphan Expenses

« on: November 01, 2023, 03:30:56 PM »

Production Proposals / September 2023 Orphan Expenses - Cameroon One

« on: September 24, 2023, 06:33:28 AM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 7MM bbp (approx $600) covering a high proportion of the orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Active Discussions / BiblePay Dynamic Sanctuaries

« on: September 18, 2023, 05:08:42 PM »

BIBLEPAY DYNAMIC SANCTUARIES

Our wallet gives you the ability to choose the size of the sanctuary you can afford. Choose between Altar (455,001 collateral), Sanctuary (4,500,001 collateral), or Temple (45,000,001 collateral).

This gives you the ability to participate in BBP rewards no matter what your budget is: small, medium or large.
The Altar pays at a rate of 10%, the Sanctuary 100%, and the Temple at 1000% of the block reward rate.

You can run your sanctuary in Active or Passive mode.

For active sanctuaries you will receive a 100% reward, while passive sanctuaries receive a 50% reward.
Passive sanctuaries are a good place for people to lock latent BBP funds to earn a reward.
Each sanctuary automatically mines blocks, and only sanctuaries may mine on the BBP network, giving the sanctuary both the mining reward plus the Sanctuary reward.

Sanctuaries perform important functions such as Instant Send Locking (facilitating instant transactions), Chainlocks (preventing 51% attacks), Governance proposal payments, LLMQ Quorums, and they even provide blocks for our network creating a strong backbone for the BBP network.

With deterministic sanctuaries, all payments are stored in an orderly fashion, in an ordered list on chain and paid round robin in order.

This feature accomplishes a truly decentralized sanctuary network that latent funds can be stored in a safe way, since its Your Key, Your Funds.

I'm excited about this feature for the future of BBP. This has the potential to attract thousands of users that gave up on mining because of monopolies stealing their hashpower, and also crypto enthusiasts who believe in the future investment power of crypto as an alternative to conventional banking to store latent BBP.

Active Discussions / Nov 2023 - Latter Rain Release

« on: September 17, 2023, 04:29:40 PM »

November 2023 Release - Latter Rain

Welcome to TestNet - Latter Rain!

Testing Starts: September 18th, 2023
Testing Ends: November 1, 2023

In this thread we will be testing:

- New sanctuary sizes (Altar, Sanctuary, Temple) with collateral amounts (455,001, 4,500,001, and 45,000,001) and corresponding payments of (10%, 100%, 1000%)
a. Verify each size of sanc can register properly and appear in the deterministic masternode list
b. Verify the payment amount on each sanc
c. Verify the chain can sync from 0 after we solve some temple blocks
- Verify the monthly superblock still works and emits and is the correct amount
- Our background batch job has been retired (ReviveSanctuaries); this is because now investors should not interfere with LLMQ quorums
- Verify Quorums form for Temples only (this increases the reliability for Chainlocks)
- Verify Temple and Altar coins in wallet lock in coin control and require an unlock (like regular sancs) so they dont get spent by accident
- Verify inactive sanctuaries (IE investor nodes) receive 50%
- Verify masternodelist shows the Tribe for a Temple
- This release includes a fix in RX miner to sleep after solving a block in MAINNET to attempt to prevent the CLSIG (Chainlock) lagging block scenario
- Cutover height 192200

Explain Changes to Entire BiblePay Network:

- Explanation of the Sanc sizes and benefits:

https://forum.biblepay.org/index.php?topic=945.new#new

- Explain usage instructions

Wiki Articles:

Older - Create a Sanc:
https://wiki.biblepay.org/Create_Sanctuary

Starting Version: 0.17.4.4:

(Please ensure your version is greater than this, in order to sync. See post #2 for current hash.

Testnet Download Links:

Ready:
Windows 64-bit: https://biblepay.org/biblepay64develop.exe
Linux 64 bits II (QT/biblepayd/biblepay-cli) zip: https://biblepay.org/bbp-lin-develop-64.zip

NOT READY (ask before trying):
(Inquire first before downloading) MacOS QT: https://biblepay.org/biblepay-harvest-develop.dmg

To self compile:
git pull origin develop

https://github.com/biblepay/biblepay/blob/develop/BuildBiblePayDevelop.txt

CONFIGURING FOR TESTNET:

Create a biblepaytest.conf file with the following contents:
testnet=1

Place the file in ~/.biblepay

Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepay/testnet3 folder.

NOTE: If you only have one machine, you can run in testnet side by side a prod node.

To create a TestNet Sanctuary:

https://wiki.biblepay.org/Create_Sanctuary

__________________________________________________________________________________________________________________________________________________________________________________________

OUR BIBLEPAY CORE TESTERS

#1 - Oncoapop

#2 -

#3 - Rob Andrews

#4 -

Production Proposals / June 2023 Orphan Expenses Cameroon One - End of June

« on: June 11, 2023, 06:53:38 AM »

Quote from: Rob Andrews on May 13, 2023, 02:41:44 PM

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 1.8MM bbp (superblock limit) covering a small proportion of our 35 orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Production Proposals / June 2023 Orphan Expenses - Cameroon One

« on: May 13, 2023, 02:41:44 PM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 6MM bbp (approx $500) covering a high proportion of our 35 orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Production Proposals / May 2023 Cameroon One Expenses

« on: April 20, 2023, 07:41:03 PM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 7MM bbp (approx $600) covering a high proportion of our 35 orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Production Proposals / April 2023 - Cameroon-One Orphan Expenses

« on: April 02, 2023, 07:08:57 AM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 8MM bbp (approx $600) covering a high proportion of our 35 orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Production Proposals / March 2023 - Cameroon One Orphan Expenses

« on: March 04, 2023, 07:45:17 AM »

We currently sponsor 35 orphans from cameroon-one, and this proposal is for the primary payment to cameroon-one.

I am seeking 8.4MM bbp (approx $600) covering a high proportion of the orphans (we pay $40 per month for each orphan).

Payout going directly to cameroon-one: BF6qmwBMmnmb4FbSmRGTeWQL1m3rwh5n7b

Pages: [1] 2 3 4 5 6 7 8 ... 11