Bible Pay

Recent Posts

Pages: 1 2 3 4 5 6 7 [8] 9 10
71
Happy new Years, Loyal BiblePay enthusiasts!

Note that unfortunately, SouthXChange is going out of business:

Please withdraw your coins.

I think our main exchange will be Bololex now:
https://bololex.com/trading/?symbol=BBP-USDT

I just tested a withdraw on bololex, and it worked, so we appear to be good!

Good luck and God bless you.

72
Production Proposals / Jan 2024 Orphan Expenses - Cameroon-One
« Last post by Rob Andrews 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

73
May the Christmas Spirit and the Glory of God fill your houses.

74
Announcements & Fundraisers / Re: Empowerment!
« Last post by Rob Andrews 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
75
Production Proposals / Dec 2023 cameroon-one expenses
« Last post by Rob Andrews 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

76
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.



77
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.

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
78
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.

79

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.


80
What kind of issue are you having?
Maybe what leads up to it also, thanks!


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."
}
Pages: 1 2 3 4 5 6 7 [8] 9 10