Bible Pay

Recent Posts

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

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

Brother Rob,
still the same today...
3
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.

Brother Rob,
still the same today...
4
Rob the community wants to know are you still there?
5
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.

6
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...
7
This is so messed up! I thought we were going towards user-friendly interface but now back to the not so user-friendly interface!
I know we do not have bunch of users, but this layout is difficult for new users.
Long Live BBP!
8
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.


9
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.
10
Does anyone know Bob personally, and could reach out to him?
Pages: [1] 2 3 4 5 6 7 8 ... 10