Messages

1

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: November 23, 2024, 01:28:36 PM »

Biblepay - v0.21.5
Mandatory Upgrade

Summary of Changes:


- Added NFT add,edit,delete capability to core wallet.
- Reinstituted SideChain transactions.
- Incremented min_masternode_proto_version to 70783 so as to facilitate a mandatory upgrade for LLMQ messages.
(Requires Temples to enforce our global LLMQ).
- Added CheckMemPoolTransactionBiblepay, which is our facility
to check mempool txs.  In this version we enforce the NFT buy rules, to allow the safe transfer of NFT.
- Reinstituted embedded sTxOutMessage in CreateRawTransaction (allows longer messages, such as NFTs to go in the chain).
- Prevent Sancs from continually adding false governance triggers due to a bug.
The code checks for an existing govobj first, and also caches the last one created (preventing dupes).
- Ensure sancs do not vote on triggers that already won.
- Make temples handle WatchmanOnTheWall, but not Sancs.
- Added exec listnfts.
- Removed UI deadlock (affecting various RPC commands
like sendrawtransaction and upgradesanc, and possibly the LLMQ
timeouts).
- Modified the LLMQ rules to work with Temples.
- Modified Pose background thread to only deal with one
sanctuary at a time (solves the deadlock).

Github:
https://github.com/biblepay/biblepay/releases

 You can download the wallet for windows from either Github or www.biblepay.org.

2

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: November 23, 2024, 05:08:03 AM »

Hey Rob,

So when you issue the command upgradesanc, usually, its not actually a "crash" (crash means that the wallet either threw an unhandled exception and ended the program), but instead was sitting there with no RPC response, right?
Yes, but 3 minutes it's not enough.
After al lot of time, hrs, still "hang" and need to be killed.
 
"Masternode command at Italian time"

10:44:48
masternode status

10:44:48
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}


Now, the question is:
How many time need the ProTx to appear on the chain ?

Thanks

Hi Ale,
Sorry for the delay, I have been working on re-creating our native NFT feature on chain rather than in arbitrum.

I guess your machine is slightly different than mine, because I was seeing a 3.1 minute delay, but, I am glad you confirm it is not a crash, yes.
One hint to avoid that altogether is to just restart the wallet then do the upgradesanc within 10 mins of rebooting, and you should not see the deadlock.  I have discovered where that is in the code and will be pushing an update any day now once fixed.

Regarding this question "How many time need the ProTx to appear on the chain ?"
It just needs to appear once.

3

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: November 10, 2024, 06:26:07 AM »

Rob, brother.

The wallet is crashed during the "exec upgradesanc AltareSanto 1" command.

Now the situation is changed to this.


11:02:52
exec upgradesanc AltareSanto 0


11:02:52
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP *.*.*.66:40000 with TXID 13cb0827e303d05604481be19dab67ae401357a9c2fe48b15936cb48e03d29c6",
  "bls_public_key": "b82a0249b0323c05f89448b9246b63ac2d3c91bec2431e8596581b664ea95484382c46c718c70a92c1016c089c838f2b",
  "bls_private_key": "61a3a78031ebf958832fb960ded4160f353d64a16591e286a41a2713713133b8",
  "pro_reg_txid": "0300010001df2ed6b028f35f75f28d21cb82bd415901acef3edcad869ea90f126bf1920f2a0100000000feffffff016c661903000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000c6293de048cb3659b148fec2a9571340ae67ab9de11b480456d003e32708cb130100000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0eb82a0249b0323c05f89448b9246b63ac2d3c91bec2431e8596581b664ea95484382c46c718c70a92c1016c089c838f2ba0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588ac0db6b50e182f58cc86674b55a713e6304e94b86bd611f00da54793759a5072eb00",
  "pro_reg_collateral_address": "BKcqLFDfZZUJWyaivmZR3WRMVdFCv1p6Qy",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|d8a79a5a10e600c12ee6c759e86772df3a3233de8326a72c7930d4eecc11c80b",
  "pro_reg_signature": "IGBCLghtakvYladlI8To5LJiBqeZ1z7A5FjssRSB1756C5BEH4QY+TGVwD2Y7cphWE5k7vSepP5Xz4aKxdlDV0E=",
  "sent_txid": ""
}

The IP add is masked by me


11:04:22
exec upgradesanc AltareSanto 1


11:04:22
bad-protx-collateral-01 (code -1)


The transaction message from wallet appear




11:05:44
masternode status


11:05:44
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "ERROR",
  "status": "Error. Can't detect valid external address. Please consider using the externalip configuration option if problem persists. Make sure to use IPv4 address only."
}


Is this a bug or something like it ?

Thanks
Ale

Hi Lalex,

So when you issue the command upgradesanc, usually, its not actually a "crash" (crash means that the wallet either threw an unhandled exception and ended the program), but instead was sitting there with no RPC response, right?  Ive seen that behavior in this new RPC, and I believe we inherited a UI deadlock.
It does respond to me after 3 minutes however.

The bad-pro-tx-collateral error must be resolved first to get a fully functioning sanc.  It means that your collateral has either not been sent or not matured.  I would start over, and when you do your 'getrawtransaction txid ordinal' ensure it is actually there, has the right amount, and has matured a few blocks before going to the next step.

4

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: October 29, 2024, 04:00:36 PM »

Dear brothers.
I started the new version wallet and synched well.
I executed the masternode status command, below the results..... I'm on right way ?

15:43:13
masternode status


15:43:13
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "[::]:0",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}

Thank you...

Yeah, you seem to be on the right track.
If you did an exec upgradesanc, the protx went out, but it takes a few blocks to register itself.

Just try the status again after a couple hours.

5

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: October 09, 2024, 05:49:23 AM »

Without going into all the boring technical details, we adopted CockroachDB as our back-end decentralized database in hopes that Temples could run an instance of CockroachDB, and that would be the storage engine of choice for us to host the sidechain.

Most of the hurdles were solved, like the HTTPS certificates, the automatic syncing, the install, the data format, the blocks, the content, etc.
However, one thing ended up killing the project in the end (and it is very similar to other non decentralized clustered databases):  It does not gracefully handle the loss of nodes during volatile periods.  We had 3 nodes in the cluster for months without a problem but after some expirimentation, I found that if BBP temples would join/unjoin sporadically, it would corrupt the database, and after spending an exorbitant amount of time to try to restore the db in those situations, I realized its just not going to work for us long term. 

So Im back to creating our own flavor of decentralized dbase, one that the Users own (I wont even be required in this project once I check in the code); all the keys are going to belong to the Temples who run this dbase.  Im migrating cockroach data down to JSON first.  Working on this in the background.

So to keep this decentralized it looks something like this:
- You host a temple
- Your temple runs this BBPDB
- Keys and configuration are embedded in the program, so Im not required

A second project is required for our Phone and Storj storage:
- Since Storj hosts our video content
- Since our PBX provides phone service
- We need a generic layer that will allow more than one, preferably 3, users to "volunteer" to run a "service type" (like phone or storage),
and the code will encrypt the keys, and use them in the temple.  Then when people drop off who no longer host a PBX or a Storj account,
they will get replaced with the other keys automatically.  This would be similar to a decentralized "market making" service.

This way I will not be needed for that particular function, and its keys can be used and protected by a temple (node).


So that is the plan for the time being and Im actively working on the BBPDB.

6

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: October 09, 2024, 05:38:54 AM »

Does anyone know Bob personally, and could reach out to him?

Are you all referring to me?
I'm fine, just havent been on the forum with all the IT projects going on.
I'll have to elaborate on the CockroachDB, that is the biggest problem right now.
I spend over 200 hours getting CockroachDB to behave in a decentralized way for BBP, and at the end, its not going to work for us.

7

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: September 05, 2024, 07:25:24 PM »

Hi Rob,

Sorry, I didn't see this until now.

Thanks for acknowleding my post.

Yes, you understand what I'm saying.  It's up to you of course.  Its a type of design philosophy, UX as they say these days. 

User Experience (UX) is a big thing today in programming. 

I am upgrading to the wallet that was just released and will get it synced.

Sounds good.
You can always try to create an altar on the new version; and I look forward to our UX project.

8

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

« on: August 18, 2024, 03:19:56 PM »

Anyone who wants to test RDP, lets continue testing this feature:

https://wiki.biblepay.org/RDP

The feature is part of the MainNet wallet.

Please launch it from there and comment here.

9

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: August 18, 2024, 03:18:19 PM »

The new wallet comes with BiblePay RDP, a feature that allows you to Remote Desktop (RDP) from one machine to another through a sanctuary.

You can read about it here:

https://wiki.biblepay.org/RDP

Lets talk about it in the TestNet thread, here:

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

10

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: August 17, 2024, 07:30:37 PM »

BIBLEPAY v0.21.3
Mandatory Upgrade
For entire network including Sancs
Cutover Height: 526500
Release URL:
https://github.com/biblepay/biblepay/releases/tag/v0.21.3
https://www.biblepay.org/wallet/
Source code:
https://github.com/biblepay/biblepay/
Self build guide:
https://github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt

Note: Because we missed a few critical versions of Dash over the last year and the format of the Sanctuary record has changed, we will need to recreate our sancs.
Sorry for the inconvenience.

To get a safe start, I have recreated 3 of my sancs already and therefore the LLMQ's will be forming over the next 24 hours (that will allow instantsend and chainlocks to re-enable ~Aug 18th or so).

IMPORTANT:  Once you upgrade, be sure to restart with -reindex=1 if you have any trouble syncing to the latest block height.
Reference hash and height:
getblockhash 524382
hash: 000005b1821c81863ff01d949aa6efe35d03d72e6bea18fb1280ca722d4f7bb4

Block Explorer (Chainz) has upgraded:
https://chainz.cryptoid.info/bbp/


Good luck, and God Bless You.

PS As usual, you can create an altar, sanc or temple to become a sanctuary miner (and this puts your latent BBP to use giving you earnings).

11

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

« on: August 14, 2024, 08:59:53 PM »

Looks like testing passed.

Thanks to all who helped test the wallet.

12

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

« on: August 10, 2024, 05:06:48 AM »

So I created a Temple, and received payment and it is working as intended.
In my prior wave I created an altar and it is also receiving the correct amounts.

Wallet testing is coming to a close.

However I have a really positive surprise for this release that Im on the final stretch on.
We have something additional called BiblePay Extensions.
This menu option gets included with the new EXE, and it allows our development team to release BBP "Modules" or extensions that extend the code base.
These get upgraded automatically when versions change (due to bugs found in the extensions and feature releases in the extensions).

The first actual extension or use case is RDP.  This allows you to RDP from your work to your BBP machine or your BBP machine to work etc (actually its BBP machine to BBP machine).
One real use case for the BBP network to send the traffic through a sanctuary and back to your desktop.
The traffic is encrypted and private and the sanctuary cannot see it either because of the encryption and the keys.
It uses the BBP keypair as an "RDP address" to connect to etc.

Ill get this final leg finished and let you all know when we can test RDP 1.0 and BBP Extensions.

13

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

« on: August 10, 2024, 05:03:11 AM »

Yep it seems to be working as intended.

I'm good my friend, i hope you are well too.

Heh Bro, thanks for the confirmation.
Im glad you got it.  This wallet seems to be pretty solid.  I sent myself tx's over the last 2 weeks and they all got IX'd and chainlocks is still up.
Must have been an inherent problem in the old code base with both of those things as chainlocks never worked correctly in the old wallet.
So Im very happy about that, that this will be a great blessing for us when we go live.

14

BiblePay Current Discussion / Re: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

« on: August 08, 2024, 06:15:36 AM »

Hi Rob,

I was thinking about Biblepay today and thought I would share some experience I have being in the space since 2016.

Some coins I notiiced were coins by software guys for other software guys.  It was very hard to keep up with the wallet, things were explained as cryptically as possible, using a lot of private jargon and the coins ended up not having very big teams.

Other coins were created by software developers for the general public and those coins tended to do better.

I still have a BBP balance and booted up the wallet to sync, and just wanted to share that with you.

I don't mind not getting anything from running the wallet since staking has been taken away (this is a tangent to my point, maybe it's not taken away, maybe it's called something else, etc.).  But like probably most supporters, there are
a lot of things I can do for the Lord and his people.  I went to the Jesus march in downtown Seattle yesterday.  Only two people in my church went, etc. etc.

I want to support Biblepay, but if it's going to take a big learning curve to use, not sure how much I am going to want to use it as life is complicated enough.

Hi CB,

Ok, I think I understand your point.  Your point is that there is going to be low adoption if it requires extremely high technical details to set the wallet to earn rewards.
I think what has happened is over time as we kept changing, we had releases where it was easy at one point but that got replaced by something new, and it became hard again.  Every time we release a new wallet the features that made it easy have been removed again.  It is certainly possible to make an "Easy Altar" feature.

The summarized answer is:
- We do still have rewards for small, mid, and large wallets.  They are altars, sancs and temples.  (All pay the same %s, but are different size collaterals).
- It would be beneficial for us to make an Easy Altar feature.
- Our next wallet is due out within 30 days, and then we have a base that we can add the feature into.

If this sounds right let me know and when the next core wallet is released we can work together in testnet to making something that is easy to set up for a newbie?

15

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

« on: July 25, 2024, 05:27:52 AM »

Hi Rob,

my testnet address is yZ4LmikQgzq5q1sc9SRsyQ4JeKDw4YCSme, sorry had a busy weekend missed your message.

Hi Bro Budinga,

Sent 525K to your testnet.  If you want to make sure it went via instantsend just look for the blue lightning bolt symbol.  Also you can check the Info tab of the wallet and look for a chainlock hash on the current block.

I hope you are doing good.