BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

Hi Rob!

I signed in over at the testnet thread, will try to squeeze some time for testing this great idea.

Bololex never attracted me for some reason, now I know why. So unfortunate, many great coins face the same challenge of exposure. Once mainstream exchanges drop out of the picture, communities fall into the hands of smaller (and in most cases shady) exchanges. DEX is the way to go, both for decentralization and peace of mind.

Before we write the specs on stone, may I suggest discussing if we could make provisions for extra functionality?

1. Would adding other coins (which are also struggling to find a place to be listed) into this mini-DEX possible?
2. Could the model be developed into something where BBP itself is consumed/locked as "gas", commision, or collateral so that demand for our own beloved coin increases?

As always, I want to thank you for the effort and time you are putting into this. One other coin you developed was the reason I started mining crypto, and BBP has been a successful sequel for me. Everyone is entitled to their own views, of course, but for me, creating value for humanity, science and democracy is a top objective of crypto.

No matter what the outcome, keep your chin up bro. This project has done more good for the needy than many millionaires around the world

Hi Talisman,
Good to hear from you, and, thank you for the kind words and good advice.

Great, Im glad you will be able to help test.

Yes, I'm dissapointed that BBP fell into that area where we were sort of on the desperate side to have an exchange, and ended up with going through this era of small shady exchanges -- who ended up having no integrity in the end.  Hopefully once God opens the door, we then see success and prosperity going forward.

Regarding the great idea of listing other small coins who have no avenue for an exchange, and using BBP as "gas", it did cross my mind already and is not completely impossible.  So Id say there are a few aspects here: 1) Do I support the idea, because I have a heart for those projects: YES, 2) Do I like the idea of being a DEX that serves other communities: YES, and now lets shift gears however to a couple hurdles.  I do feel there has to be a minimum level of activity and testing done first on our own exchange before we expand into the full DEX feature - another words, I will do some hard work to get this out and if we can get a certain amount of traffic flowing through this thing we can take the next logical step and possibly add another trading room for another currency.  Last piece of this is, there will be certain minimum technical requirements just to list another coin.  Probably on the order of one of our sanctuaries running their wallet and us coming up with a standard API that uses the alt-currencies BlockExplorer API to validate UTXOs that are "settled".  The reason this becomes an issue is because the mining rule will pause OCO AtomicTx's that rely on the foreign currencies UTXO to be settled at certain heights which could slow down our miners if not done right.  And then there is the perpetual cost of running one BX/AltNode for each listed currency that someone has to either volunteer for or pay for etc.  So lets keep this in mind.  As far as architecture, yes, I will keep this in mind to make sure its not going to be extremely hard to shoe horn in once we go down there.

As far as where we are now, I think the feature is 65% finished.  Know that in 1.0 its going to be all RPC but of course, pie in the sky idea is if we ever take off, we can add a GUI to the core wallet (woudlnt that be amazing to have a GUI trading room in a core wallet lol).

Ill post again this weekend with more finer updates in the TestNet thread also.

Have a great week.

As promised, one small update first:

The technical hurdles were solved for atomic trading (IE the hard stuff, the punchlist of 35 items) etc.  But there is one technical issue holding up my progress, so we need another 7 days before testnet is ready; but I think overall its good and on schedule for testing soon.

I wanted to also comment on one of the prior comments that I made:
The huge advantage to having a decentralized DOGE exchange in the wallet is that it is equivalent to being listed on every exchange in the world.  Someone asked why.  Thats because first of all, DOGE is listed EVERYWHERE.  So this is  similar to 'virtually' being listed on the top 10 exchanges - think Binance, HitBTC, Coinbase, etc.  Of course as mentioned, there is no real volume in the wallet so no, we have no trading volume or real liquidity in the wallet yet.  But otoh, you can trade in and out of DOGE, meaning that I can trade out in Kenya, India, US, anywhere.  Thats quite amazing, isnt it?

Finally, I noticed Bololex came back on and I was able to withdraw BBP successfully.  Great news, no funds are lost for our users!

Hi CB, good to see you tonight and God bless you.
Thats cool you used to have a software company.  What software did you sell?  Good luck too.

Hi Rob,

I meant to answer this question but have been elsewhere.

I created ParaMind Brainstorming Software, the first generative brainstorming program in Windows.  We first started selling copies in 1993 and have sold them up until about three years ago.  There is a video "The Mother of All Prompts" which shows the ParaMind algorithm, which one can see from our examples page at our website.

It's been mentioned in various books, including one by Ray Kurzweil.

Hi Rob,

I meant to answer this question but have been elsewhere.

I created ParaMind Brainstorming Software, the first generative brainstorming program in Windows.  We first started selling copies in 1993 and have sold them up until about three years ago.  There is a video "The Mother of All Prompts" which shows the ParaMind algorithm, which one can see from our examples page at our website.

It's been mentioned in various books, including one by Ray Kurzweil.

Hi CB,

Ahh, ok, ParaMind, hmm, I never heard of that but I have it on my list to check out now!

The DOGE/BBP Atomic Tx is ready for testnet; will post about it there.

https://forum.biblepay.org/index.php?topic=971.0       

Hi CB,

Ahh, ok, ParaMind, hmm, I never heard of that but I have it on my list to check out now!

Yeah, I read about ParaMind, interesting software. It seems like you were 20 years ahead of the AI race, at least in some respect.
I saw the output of the long merge
https://www.paramind.net/bdt1mrge.html
When I read that I thought, maybe it would be useful to apply weights to each row added and somehow provide the top 20 to the user.  But then thats a long discussion.

Have you seen Princeton's paper on Word Embeddings in Geometric Algebra?

https://www.pacm.princeton.edu/sites/default/files/pacm_arjunmani_0.pdf


This is one of the bigger foundations of modern day AI models; in the NLM, one of the low level (initial learning side) algorithms apply a distinct int(eger) to a word, and then the intelligence amplification process, forms a base relationship (kind of like our ECDSA point on a plane) between words and subjects, such as the relationship between " a man is to a King as a Woman is to ___".  So on a graph, you can look at the linear relationship of the points and where they cross, you have an NLM relationship (IE the subject is similar and the relativity is calculatable using math).  Maybe you can use that algorithm to apply weights to subjects that are related, and write a successor etc.

Biblepay v022.8 - Mandatory Upgrade
https://github.com/biblepay/biblepay/releases/tag/v022.8-Mandatory

- Lower Tx fee down to .000001 so we can trade assets with very low tx fees in trading rooms
- Add BBP atomic trading v2.0 and underpinnings
- Add colored coins (which are colored assets) and add one asset: DOGE, which is BBP Wrapped Doge
- Add sendasset (send colored asset from BBP wallet to BBP wallet) and getassetbalance
- Add memory pool rule to reject tx's that violate the colored asset protocol
- Remove colored assets from coin control and accidental wallet spending
- Add background thread to mine first colored DOGE asset address
- Add createassetaddress, which will allow you to create another asset address like BBP-Wrapped-DASH, etc.
- Add exec bankroll, which creates denominated bbp vout transactions.
- Add exec wrap and exec unwrap. This allows you to WRAP doge, and Unwrap doge (or other assets).
- Add getassetbalance to query the colored asset balance by asset type.
- Added TEST version of our next trading room (see testnet thread)

Biblepay v022.8 - Mandatory Upgrade
https://github.com/biblepay/biblepay/releases/tag/v022.8-Mandatory

- Lower Tx fee down to .000001 so we can trade assets with very low tx fees in trading rooms
- Add BBP atomic trading v2.0 and underpinnings
- Add colored coins (which are colored assets) and add one asset: DOGE, which is BBP Wrapped Doge
- Add sendasset (send colored asset from BBP wallet to BBP wallet) and getassetbalance
- Add memory pool rule to reject tx's that violate the colored asset protocol
- Remove colored assets from coin control and accidental wallet spending
- Add background thread to mine first colored DOGE asset address
- Add createassetaddress, which will allow you to create another asset address like BBP-Wrapped-DASH, etc.
- Add exec bankroll, which creates denominated bbp vout transactions.
- Add exec wrap and exec unwrap. This allows you to WRAP doge, and Unwrap doge (or other assets).
- Add getassetbalance to query the colored asset balance by asset type.
- Added TEST version of our next trading room (see testnet thread)

Fantastic work my friend, good timing as Bololex is down again.
Cant wait to test the new features.

Fantastic work my friend, good timing as Bololex is down again.
Cant wait to test the new features.

Exactly, Bololex was rather inspirational.
Lets turn a negative into a positive and have the first in-wallet exchange.
Also the new architecture will support more than one coin in the future, if there is adoption.
There was a bug in the current version on windows, so once the new version is released in a few minutes we can start testing in testnet.

Here is the testnet to help us test the new DOGE-BBP exchange:

https://forum.biblepay.org/index.php?topic=971.0

Dear Ale,
Thanks for your question. I have them both behind NAT and also in a datacenter.

This is the one behind NAT.
$ cli masternode status
{
  "outpoint": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193-0",
  "service": "108.180.46.33:41000",
  "proTxHash": "f64ce28c46d989035dc00e48fd5c2906050d20ad471b9ef7188d3fc32e3365a5",
  "type": "Regular",
  "collateralHash": "a164e846e4166e9a0ecf9cfc33bc4bdc4a5676f54e430c11af3e441ce3ce8193",
  "collateralIndex": 0,
  "dmnState": {
    "version": 2,
    "service": "108.180.46.33:41000",
    "registeredHeight": 551815,
    "lastPaidHeight": 552264,
    "consecutivePayments": 0,
    "PoSePenalty": 0,
    "PoSeRevivedHeight": -1,
    "PoSeBanHeight": -1,
    "revocationReason": 0,
    "ownerAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
    "votingAddress": "B6Ud6beY9gcLwXF6j5UXTrL81hdaHqr3kL",
    "payoutAddress": "BKcbU8zYxfHGfaytRowYQLkyVA1U2BDYx4",
    "pubKeyOperator": "a8aba6cd5915acb888c5b7c689808f015b1c417d7fa9edbf3042a1ee1168ba17446cfdb1f0b5492fcaf6924629d0081c"
  },
  "state": "READY",
  "status": "Ready"
}
To make this work, as an example, I needed to go to my router IP 108.180.46.33 (get this from whatsmyip.com) and map 41000 to an internal port 41000 in this case, on my internal server 192.168.1.16 (get this from ifconfig)

Add this to your biblepay.conf

externalip=108.180.46.33:41000
masternodeaddr=192.168.1.16:41000
port=41000
maxconnections=128
masternodeblsprivkey=......132b9d4ef47f91bdc7a692820e.....

Blessings
oncoapop

Guys, I give up.
I’m stuck in this situation.
I tried everything, reinstalled wallet, changed configuration, changed IP port, updated to the latest version, all the rules of NAT on routers are fixed, if I run a netstat ports are in listen, if I run on external ip telnet on ports 40000 and 41000 the machine reachable.
All this did not help to solve the situation.

Below the output from masternode status

10:11:01
masternode status
10:11:01
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "*.*.*.66:41000",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}

Any suggestion? [/list]

Guys, I give up.
I’m stuck in this situation.
I tried everything, reinstalled wallet, changed configuration, changed IP port, updated to the latest version, all the rules of NAT on routers are fixed, if I run a netstat ports are in listen, if I run on external ip telnet on ports 40000 and 41000 the machine reachable.
All this did not help to solve the situation.

Below the output from masternode status

10:11:01
masternode status
10:11:01
{
  "outpoint": "0000000000000000000000000000000000000000000000000000000000000000-4294967295",
  "service": "*.*.*.66:41000",
  "state": "WAITING_FOR_PROTX",
  "status": "Waiting for ProTx to appear on-chain"
}

Any suggestion? [/list]

Sorry to hear you are having issues creating a new sanc.  I am sure it works as last month I created a few more (to ensure our LLMQ was working good etc).

The Sanc IP is public and announced all over the place (its in the masternode list) so it should not really have to be concealed.
If you dont want to reveal it I would try this from another machine on a network outside your LAN, like a work machine:
telnet sancip port
And see if it answers; if you do want to reveal it I can telnet from my house and tell you if it answers.

Im not sure if you are saying the problem is that you are not being entered into sanc list, or if you are in the list and are not being paid 100%.
Even a faulty setup should get you in the list and get you 50% payments (IE investor type payments).

Im not saying to be happy with that just looking for more info.

Definitely do a getnetworkstatus on each machine, and verify they are on the latest software version, and a getblockhash, verify they match chainz.
Verify the TXID that sent the 'exec upgradesanc' command is in the chain more than 6 deep.
Verify that you are in the masternodelist, even if it is the wrong IP, you should be in the list.
Then you can do an additional 'exec upgradesanc sancname' and that will fix the ip.

I always do that after I create a sanc, and after a few blocks pass as generally I have a new sanc with the wrong ip, then the exec upgradesanc fixes the ip.

You didn't post the current mandatory wallet upgrade of 2/8/25 to this thread.

https://github.com/biblepay/biblepay/releases/tag/v022.9-Mandatory

Sorry to hear you are having issues creating a new sanc.  I am sure it works as last month I created a few more (to ensure our LLMQ was working good etc).

The Sanc IP is public and announced all over the place (its in the masternode list) so it should not really have to be concealed.
If you dont want to reveal it I would try this from another machine on a network outside your LAN, like a work machine:
telnet sancip port
And see if it answers; if you do want to reveal it I can telnet from my house and tell you if it answers.

Im not sure if you are saying the problem is that you are not being entered into sanc list, or if you are in the list and are not being paid 100%.
Even a faulty setup should get you in the list and get you 50% payments (IE investor type payments).

Im not saying to be happy with that just looking for more info.

Definitely do a getnetworkstatus on each machine, and verify they are on the latest software version, and a getblockhash, verify they match chainz.
Verify the TXID that sent the 'exec upgradesanc' command is in the chain more than 6 deep.
Verify that you are in the masternodelist, even if it is the wrong IP, you should be in the list.
Then you can do an additional 'exec upgradesanc sancname' and that will fix the ip.

I always do that after I create a sanc, and after a few blocks pass as generally I have a new sanc with the wrong ip, then the exec upgradesanc fixes the ip.

Rob,
My wallet is uncrypted. can be this the problem ?
[/list]

Rob,
My wallet is uncrypted. can be this the problem ?
[/list]

Rob,
My wallet is uncrypted. can be this the problem ?
[/list]

Verify that you are in the masternodelist, even if it is the wrong IP, you should be in the list
I'm not in the list
The machine is reachable from outside network by telnet on por 41000 and the demon is in listen

15:36:04
getnetworkinfo


15:36:04
{
  "version": 2209,
  "buildversion": "v0.22.9 Great-Awakening",
  "subversion": "/BiblePay Core:0.22.9/",
  "protocolversion": 70784,
  "localservices": "0000000000000c05",
  "localservicesnames": [
    "NETWORK",
    "BLOOM",
    "NETWORK_LIMITED",
    "HEADERS_COMPRESSED"
  ],
  "localrelay": true,
  "timeoffset": 1,
  "networkactive": true,
  "connections": 10,
  "inboundconnections": 0,
  "outboundconnections": 10,
  "mnconnections": 4,
  "inboundmnconnections": 0,
  "outboundmnconnections": 4,
  "socketevents": "select",
  "networks": [
    {
      "name": "ipv4",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "ipv6",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "i2p",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    }
  ],
  "relayfee": 0.00000700,
  "incrementalfee": 0.00000700,
  "localaddresses": [
    {
      "address": "*.*.*.66",
      "port": 40000,
      "score": 4
    }
  ],
  "warnings": ""
}


Netstat command from windows shell/cmd

TCP    192.168.68.208:40000   verunix:56860          ESTABLISHED
TCP    192.168.68.208:40000   ip109:45890            ESTABLISHED
TCP    192.168.68.208:40000   vmi2331614:40804       ESTABLISHED
TCP    192.168.68.208:40000   seven:51086            ESTABLISHED
TCP    192.168.68.208:40000   seven:53327            ESTABLISHED
TCP    192.168.68.208:40000   vmi690434:45594        ESTABLISHED
TCP    192.168.68.208:40000   108.180.46.33:44924    ESTABLISHED
TCP    192.168.68.208:40000   108.180.46.33:58966    ESTABLISHED
TCP    192.168.68.208:40000   vmi2331596:56606       ESTABLISHED
TCP    192.168.68.208:40000   vmi2331597:36226       ESTABLISHED
TCP    192.168.68.208:40000   174-47-79-220:62306    TIME_WAIT
TCP    192.168.68.208:40000   vmi674906:58334        ESTABLISHED