271
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: December 18, 2023, 06:32:38 AM »
May the Christmas Spirit and the Glory of God fill your houses.
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.
272
Announcements & Fundraisers / Re: Empowerment!
« on: December 01, 2023, 03:03:15 PM »
Austin is a loyal member of the community who has been around for at least 3 years and he helps us out with testing and he also makes us videos.
I highly recommend helping Austin if you have the financial capabilities.
He is going to Seminary full time with a passion to be a preacher, and he is a lifestyle Christian, out on the streets praying for people.
His character is good, and he has high morals.
I wish you the best Austin in this fundraiser.
Rob
I highly recommend helping Austin if you have the financial capabilities.
He is going to Seminary full time with a passion to be a preacher, and he is a lifestyle Christian, out on the streets praying for people.
His character is good, and he has high morals.
I wish you the best Austin in this fundraiser.
Rob
273
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
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
274
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: November 23, 2023, 12:01:10 PM »Thanks Rob,
So first of all in the location " %appdata%/Biblepay " there isen't the file " deterministic.conf ". I create it manually
After execution of " upgradesanc altare 1 " i have the error belowe:
14:56:29
exec upgradesanc altare 1
4:56:30
bad-protx-collateral-check-proreg-tx (code 16) (code -1)
I think the 1st issue is on a create the sanctuary altar but really don't understand why.
Thanks
Ale
Hi Lalex,
So thats probably normal that deterministic does not exist yet, because it is created after a successful "upgradesanc". We automatically create Or append an entry in there whenever you add a sanc.
So on the root issue, upgradesanc altare 1 not working because collateral does not exist, if you could please go back a step, and ensure the "altare" sanc has the proper collateral referenced in the "masternode.conf" file.
Here is an entry from mine to show you the structure:
altar1 192.1.168.2:10001 mnp 476181e8236bf7e51feea7a1e325691b6d2d3d30e0d5ff4a31367df6ee906xxx 1
Note that the TXID and vout ordinal must be correct and populated. You can check by doing a command like this:
getrawtransaction txid 1
If that responds, you can see the vout ordinal in the command to make sure it matches the one in the masternode.conf.
275
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: November 18, 2023, 07:17:15 AM »
Just getting everyone warmed up for the next phase of development on BBP.
We have some major camps in Crypto, with BTC being the King and giving the user the ability to send digital cash with the users balance is the sum of their wallet addresses unspent outputs. Their code is relatively pristine in that they do not like to add a bunch of things (other than misc data) to the blocks, and therefore leave other use cases to be off the blockchain (like lightning network).
Ethereum, a virtual state machine computer, maintains a ledger of balances and allows smart contracts to be stored and run in provable sequence as blocks tick by. Both users can have balances, and contracts can have balances. One distinction is that Ethereum allows balances to be transferred by Account (similar to XRP), rather than UTXO.
And then we have Storj, who has over 5000 mining hard drives storing fragments of files around the world. So they provably allow reconstruction of files pointed to by transactions. Essentially file storage on the blockchain, but still require gateways to be added downstream to make sense of all the cool storage.
Revisiting the Difference Between UTXO and Account Balance Model
UTXO and Account Balance Models are two different ways to track funds and transactions; Bitcoin uses UTXO, while Ethereum uses the Account Balance Model.
Bitcoin is based on the UTXO blockchain model where a transaction is divided into different parts – inputs and outputs. The user’s wallet balance keeps track of all the UTXO transactions.
Ethereum is based on the Account/Balance model. This model ensures that the account balance is large enough or at least equal to the transaction amount to be spent.
In general, most developers consider the UTXO model to be more secure and it requires less storage compared to the Account/Balance model, which needs more storage for big blocks of data.
So in summary we have:
BTC -> Ability to transfer cash easily. Pros: A pristine codebase. Cons: Functionality must be built off the chain.
DASH -> Instantly transfer cash with instantsend. Pros: A reliable way to instantly send money, developed Masternodes. Cons: Cannot execute code contracts or store massive amounts of data.
ETH -> A virtual state machine executing smart contracts. Pros: Smart contracts for financial purposes can be transacted. Cons: Limited variable states per contract can be memorized, and only limited data storage can be represented. Expensive tx fees when busy. NFTs are simply URL pointers that can die after a while.
BBP -> "The plan can be discussed" to make a place for us. The use case can be along the lines of a provable unlimited synchronized global database. This allows serialized transactions to run as blocks tick by that are synchronized across the cockroachdb nodes, and each tx will affect the state of each db sub-tier. NFTs can be rewritten using a new spec that make them immutable and more useful than now. Front end business systems can be written that will use BBPs built in tx's rather than a database. BBP itself can use its own storage system to replace its database storage for Expenses, Revenue, Videos, Timeline, GospelLinks, and Email, etc.
We have some major camps in Crypto, with BTC being the King and giving the user the ability to send digital cash with the users balance is the sum of their wallet addresses unspent outputs. Their code is relatively pristine in that they do not like to add a bunch of things (other than misc data) to the blocks, and therefore leave other use cases to be off the blockchain (like lightning network).
Ethereum, a virtual state machine computer, maintains a ledger of balances and allows smart contracts to be stored and run in provable sequence as blocks tick by. Both users can have balances, and contracts can have balances. One distinction is that Ethereum allows balances to be transferred by Account (similar to XRP), rather than UTXO.
And then we have Storj, who has over 5000 mining hard drives storing fragments of files around the world. So they provably allow reconstruction of files pointed to by transactions. Essentially file storage on the blockchain, but still require gateways to be added downstream to make sense of all the cool storage.
Revisiting the Difference Between UTXO and Account Balance Model
UTXO and Account Balance Models are two different ways to track funds and transactions; Bitcoin uses UTXO, while Ethereum uses the Account Balance Model.
Bitcoin is based on the UTXO blockchain model where a transaction is divided into different parts – inputs and outputs. The user’s wallet balance keeps track of all the UTXO transactions.
Ethereum is based on the Account/Balance model. This model ensures that the account balance is large enough or at least equal to the transaction amount to be spent.
In general, most developers consider the UTXO model to be more secure and it requires less storage compared to the Account/Balance model, which needs more storage for big blocks of data.
So in summary we have:
BTC -> Ability to transfer cash easily. Pros: A pristine codebase. Cons: Functionality must be built off the chain.
DASH -> Instantly transfer cash with instantsend. Pros: A reliable way to instantly send money, developed Masternodes. Cons: Cannot execute code contracts or store massive amounts of data.
ETH -> A virtual state machine executing smart contracts. Pros: Smart contracts for financial purposes can be transacted. Cons: Limited variable states per contract can be memorized, and only limited data storage can be represented. Expensive tx fees when busy. NFTs are simply URL pointers that can die after a while.
BBP -> "The plan can be discussed" to make a place for us. The use case can be along the lines of a provable unlimited synchronized global database. This allows serialized transactions to run as blocks tick by that are synchronized across the cockroachdb nodes, and each tx will affect the state of each db sub-tier. NFTs can be rewritten using a new spec that make them immutable and more useful than now. Front end business systems can be written that will use BBPs built in tx's rather than a database. BBP itself can use its own storage system to replace its database storage for Expenses, Revenue, Videos, Timeline, GospelLinks, and Email, etc.
276
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: November 17, 2023, 06:24:19 PM »
15:50:39
exec revivesanc altare
15:50:39
{
"Command": "revivesanc",
"Error": "Unable to find sanctuary altare in deterministic.conf file."
}
15:52:23
exec exec upgradesanc altare
15:52:23
{
"Command": "exec",
"Error": "Command not found"
}
15:52:33
exec upgradesanc altare
15:52:33
You must specify exec upgradesanc/createsanc sanctuary_name (where the sanctuary_name matches the name in the masternode.conf file) 0/1 (where 0=dry-run, 1=real). NOTE: Please be sure your masternode.conf has a carriage return after the end of every sanctuary entry (otherwise we can't parse each entry correctly). (code -1)
15:53:10
exec upgradesanc altare
15:53:10
You must specify exec upgradesanc/createsanc sanctuary_name (where the sanctuary_name matches the name in the masternode.conf file) 0/1 (where 0=dry-run, 1=real). NOTE: Please be sure your masternode.conf has a carriage return after the end of every sanctuary entry (otherwise we can't parse each entry correctly). (code -1)
15:53:15
exec revivesanc altare
15:53:15
{
"Command": "revivesanc",
"Error": "Unable to find sanctuary altare in deterministic.conf file."
}
1) When you originally ran the upgradesanc command on your sanc altare, it would have appended an entry to deterministic.conf in %appdata%\biblepay.
2) Plz open your deterministic.conf file and ensure that entry is created.
Re-reading your post, I see you mentioned this
"15:52:33
You must specify exec upgradesanc/createsanc sanctuary_name (where the sanctuary_name matches the name in the masternode.conf file) 0/1 (where 0=dry-run, 1=real). NOTE: Please be sure your masternode.conf has a carriage return after the end of every sanctuary entry (otherwise we can't parse each entry correctly). (code -1)"
So actually I see your upgradesanc command didnt run.
Please try again with this instead:
upgradesanc altare 1
You just need the "1" in there to run the command for real. A "0" means to Test first.
277
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: November 12, 2023, 01:32:15 PM »
BiblePay - 0.17.5.4
Mandatory Upgrade for Sanctuaries and Users
https://github.com/biblepay/biblepay/releases/tag/0.17.5.4
- Improves block syncing and LLMQs
- Makes BBP Mac compatible (Mac builds work again)
Mandatory Upgrade for Sanctuaries and Users
https://github.com/biblepay/biblepay/releases/tag/0.17.5.4
- Improves block syncing and LLMQs
- Makes BBP Mac compatible (Mac builds work again)
278
Production Proposals / Re: Nov 2023 Cameroon One Orphan Expenses
« on: November 12, 2023, 01:21:23 PM »
Way to go, Praise God.
279
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: November 12, 2023, 10:27:13 AM »
I hope everyone is having a great November!
I'm so looking forward to the latter-rain of Jesus, where we minister to thousands and thousands.
Get ready for the wave of Muslims and Buddhists who would like to convert to Christ!
Lets learn about Islam Apologetics, and Buddhist apologetics.
Note, there will be a BBP wallet release in 4 hours.
I'm so looking forward to the latter-rain of Jesus, where we minister to thousands and thousands.
Get ready for the wave of Muslims and Buddhists who would like to convert to Christ!
Lets learn about Islam Apologetics, and Buddhist apologetics.
Note, there will be a BBP wallet release in 4 hours.
280
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: November 12, 2023, 10:19:04 AM »Dear all,What kind of issue are you having?
I try to installa an Altar but there are some errors using the easysanc procedure
Is there a post where reading the instrutoction ?
Thanks
Maybe what leads up to it also, thanks!
281
Production Proposals / Nov 2023 Cameroon One Orphan Expenses
« on: November 01, 2023, 03:30:56 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
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
282
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: October 21, 2023, 07:58:32 AM »
*** Update on our current Orphan Care Providers (our Vendors) ***
Over the last year, our sponsorship level was stable, sponsoring 44 orphans (35 from Cameroon-One and 14 from Kairos).
(I also have kept a personal relationship with Compassion.com, but that relationship is on a personal level and does not affect the BBP P&L. )
Nevertheless, with the market cap of our coin remaining low, with no new outside donations, the current size of BBP's governance superblock can only cover the Cameroon-One relationship, therefore we had to downsize this month. The downsizing caused me to pause our relationship with Kairos (one portion of our portfolio that was not able to funded at all by BBP funds, over the last year), and this required me to cancel 13 orphans with Kairos.
I did give Andrew from Kairos a 60 day notice as well so he has time to start to place the remaining 13 children with other sponsors. On another note, recently, Kairos had 6 of our children quit the program (IE they naturally dropped out due to not attending the services any longer), so this worked well as far as making it an easier transition for us to only have to cancel 13 rather than 19 children. Our balance with Kairos is approx -$1,000 (IE we have a credit), therefore the funding will last to the end of the year.
If you get a chance, thank Kairos for their great service and pray that they are blessed in the Kingdom for their continual help for the children in their care. Also pray for their church plans to be lifted to God and approved so they have a place of worship.
Current BBP Portfolio Size:
https://unchained.biblepay.org/gospel/collage
Over the last year, our sponsorship level was stable, sponsoring 44 orphans (35 from Cameroon-One and 14 from Kairos).
(I also have kept a personal relationship with Compassion.com, but that relationship is on a personal level and does not affect the BBP P&L. )
Nevertheless, with the market cap of our coin remaining low, with no new outside donations, the current size of BBP's governance superblock can only cover the Cameroon-One relationship, therefore we had to downsize this month. The downsizing caused me to pause our relationship with Kairos (one portion of our portfolio that was not able to funded at all by BBP funds, over the last year), and this required me to cancel 13 orphans with Kairos.
I did give Andrew from Kairos a 60 day notice as well so he has time to start to place the remaining 13 children with other sponsors. On another note, recently, Kairos had 6 of our children quit the program (IE they naturally dropped out due to not attending the services any longer), so this worked well as far as making it an easier transition for us to only have to cancel 13 rather than 19 children. Our balance with Kairos is approx -$1,000 (IE we have a credit), therefore the funding will last to the end of the year.
If you get a chance, thank Kairos for their great service and pray that they are blessed in the Kingdom for their continual help for the children in their care. Also pray for their church plans to be lifted to God and approved so they have a place of worship.
Current BBP Portfolio Size:
https://unchained.biblepay.org/gospel/collage
283
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: September 28, 2023, 06:47:50 AM »Thank you for that. Looks okay.So far the network appears to be more stable, now that we have kicked off older sancs that are years old on any protocol version. The LLMQs are 90% correct now, but there are still two weird sancs in there that I have no idea if they are mischevious or not, will need to dig into that. But for now since the quorum has an 80% good consensus, DM IX has restarted and DM Chainlocks have restarted, all Glory to God. Now we are waiting for SX to upgrade; I notified them.
The temple appears to be receiving 16,830 bbp for when it is ENABLED but if for some reason they are out of sync, their payment is not halved but appears to be only 841 bbp (ie half a sanctuary's). Is this expected and correct behaviour?
Since the temple is the only BBP wallet running on the server, we have no way of knowing when it is out of sync, At least if there were 10 sancs as a temple, I could calculate the consensus and reset the lagging sancs. The only that we know a temple may be lagging if it fails to receive the full payment amount.
Thank you for looking into this.
Blessings
oncoapop
To determine if your sanc is in sync, I would prefer using chainz to any internal script anyway:
https://chainz.cryptoid.info/bbp/
Regarding being docked 50%, that happens if the other nodes cant see your sanc. Try verifying you can telnet to the port from another machine to your external address.
Also, if you do not agree with chainz, do a ./biblepayd -erasechain=1 to start on solid ground as you might have started after the mandatory on your own chain.
Rob
284
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: September 25, 2023, 07:40:26 PM »
BiblePay - 0.17.4.8 - Mandatory Upgrade for Entire Network
- Added checkpoint @ 440K
- Filter out misbehaving sanc peers in LLMQ for one duration
- Prevent division by zero in LLMQ class
- Require Sancs to be on protoversion >= 70790
- Enable ReviveSanctuaries batch job for Altars and Sancs but not Temples
- Edit release name to be 'Latter Rain'
Github Release:
https://github.com/biblepay/biblepay/releases/tag/0.17.4.8
- Added checkpoint @ 440K
- Filter out misbehaving sanc peers in LLMQ for one duration
- Prevent division by zero in LLMQ class
- Require Sancs to be on protoversion >= 70790
- Enable ReviveSanctuaries batch job for Altars and Sancs but not Temples
- Edit release name to be 'Latter Rain'
Github Release:
https://github.com/biblepay/biblepay/releases/tag/0.17.4.8
285
BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)
« on: September 25, 2023, 07:15:36 PM »
Hey All,
A bug has been found in the newest release and since our exchanges have not upgraded yet, I am re-releasing tonight.
Thank you all for your understanding.
A bug has been found in the newest release and since our exchanges have not upgraded yet, I am re-releasing tonight.
Thank you all for your understanding.