Messages

136

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 14, 2025, 01:47:58 PM »

Check this out I just purchased these 5 sell orders which is 1.48 doge but only 0.1625 doge was deducted

also i recieved 7 tx of 2000 bbp when only 2 of the sell orders were for that amount

Yeah I found the problem... The good news is, this should actually improve the service in the end to be 100% reliable (which is what we need for this to have any adoption).  The bad news is its kind of complicated and requires a mandatory.

So in our memory pool we have a set of rules where atomics can fail if they violate the colored asset protocol.  Im going to need to modify that to account for multisig txs in some cases where it is allowed to transact the non colored plus the colored in one single atomic tx, as long as the sum(colored sender amount) = spent(colored recv amount).  This will allow the tx to go out in one single atomic tx (thats not exactly how it is today).

So ill work on this next then we can have a new mandatory.  I will probably do this in a way where we just re-test everything we have now and wait for that to finish before we add the complexity of fractional fills.

Please check back over the weekend guys.

I believe we will also have to have a sanc hard fork.

137

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 14, 2025, 01:18:38 PM »

Check this out I just purchased these 5 sell orders which is 1.48 doge but only 0.1625 doge was deducted

also i recieved 7 tx of 2000 bbp when only 2 of the sell orders were for that amount

Ahh, thanks for the pics.
Luckily, I was the seller so in my wallet I was able to confirm each of these 5 tx's as the counterparty and diagnose this.

Tx 1 = height 565644, txid   f39e5eefa3e9b520d0f47622fc899ea0bb6517c6031f116969ce6ae79d9b0cb8   2000   0.000056   filled
Tx 2 = height 565644, txid   29d6b7afbfd5e225ea0e633853ff229815070d618ff323ab3fb4d9eefc116d03   2000   0.000076   filled

Tx 3 = memory-pool-error      4000   0.000076   error
Tx 4 = memory-pool-error      5000   0.000076   error
Tx 5 = memory-pool-error      7000   0.000076   error

So what is really interesting is somehow in my wallet, it sent the BBP but did not successfully sign over the remaining .22 DGZZ because of a memory pool error.  Not sure what that is, so I have to debug and try to reproduce this.

Checking

138

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

« on: February 14, 2025, 11:44:29 AM »

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

Its OK, the last prior mandatory was enough for the Sancs, now Im just working in testnet to get fractional fills out.
Once I have a hard fork we will notify again.  (IE Intentional).

139

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

« on: February 14, 2025, 11:43:20 AM »

11:44:35
exec upgradesanc AltareSanto 0


11:44:35
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP 93.55.252.66:40000 with TXID ec3e3f040b87aa37ed761b2446c49bda2c78f1517577e2e7bfe344270c580f67",
  "bls_public_key": "8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5",
  "bls_private_key": "01bc22c2b16bbc52e1705844935a79b6068342fccb942adb00e972d8063b36ac",
  "pro_reg_txid": "0300010001609e5ce9b57500890998887c7c6a050994e4c9ca104ac28336f3c8a5f22b1aa80000000000feffffff016cd2f505000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000670f580c2744e3bfe7e2777551f1782cda9bc446241b76ed37aa870b043f3eec0000000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0e8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5a0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588acd33796ed5126898ff5b10412b40b5f14a0c8f07889575fdeefa55abe12a2f8b900",
  "pro_reg_collateral_address": "BHn32VamZjQKE3iAtNWeN3LoDDsNQAr8yM",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|c36781721e1a114bf020f549e286da08375d473c77edbec707fbbf37b8d83061",
  "pro_reg_signature": "H9q/GPzVkA02knhPSv9EZb0T/nUcQF8vP5E/63qqmXOUVg9vIOnDuWTaEHocal2zc9qrlF56sZ3vY110Z2ouaXE=",
  "sent_txid": ""
}

11:44:35
exec upgradesanc AltareSanto 0


11:44:35
{
  "Command": "upgradesanc",
  "Summary": "Creating protx_register command for Sanctuary AltareSanto with IP 93.55.252.66:40000 with TXID ec3e3f040b87aa37ed761b2446c49bda2c78f1517577e2e7bfe344270c580f67",
  "bls_public_key": "8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5",
  "bls_private_key": "",
  "pro_reg_txid": "0300010001609e5ce9b57500890998887c7c6a050994e4c9ca104ac28336f3c8a5f22b1aa80000000000feffffff016cd2f505000000001976a914da266fc172389feffdd44105e460b996a3cd826588ac0000000000d1020000000000670f580c2744e3bfe7e2777551f1782cda9bc446241b76ed37aa870b043f3eec0000000000000000000000000000ffff5d37fc429c40a0761b3fffcf408d157197fa366d771db5835f0e8f2a4d78232f24d4da053012c98b4d3a8ec9c00f75339c50030c609794a49532cb75b30706820c5779479986ed17e8d5a0761b3fffcf408d157197fa366d771db5835f0e00001976a914da266fc172389feffdd44105e460b996a3cd826588acd33796ed5126898ff5b10412b40b5f14a0c8f07889575fdeefa55abe12a2f8b900",
  "pro_reg_collateral_address": "BHn32VamZjQKE3iAtNWeN3LoDDsNQAr8yM",
  "pro_reg_signed_message": "BQLYy9oNyiCdbym3Vd7dd8nqiP2xAipdYc|0|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|BK5XDb4TrZHRzTQnVEQhaqV3DbhX65b7zY|c36781721e1a114bf020f549e286da08375d473c77edbec707fbbf37b8d83061",
  "pro_reg_signature": "H9q/GPzVkA02knhPSv9EZb0T/nUcQF8vP5E/63qqmXOUVg9vIOnDuWTaEHocal2zc9qrlF56sZ3vY110Z2ouaXE=",
  "sent_txid": ""
}
[/list][/list]

Ahh! Finally I see the problem, thanks for pasting all that.

So you had been doing everything right, your tx was on the mainchain (I see it) and you are synced, and your commands were right, the problem is your collateral address does not have the right amount:

https://chainz.cryptoid.info/bbp/address.dws?BHn32VamZjQKE3iAtNWeN3LoDDsNQAr8yM.htm

Notice that you only sent 450 bbp to that.

The sancs are either:
4 500 001.00    for a Sanc  (IE 4.5MM  or 4,500,001  bbp)
45 000 001.00  for a temple
450 001.00       for an altar

Once you do this over with one of those amounts, then you will see yourself in 'masternodelist' (RPC).

140

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 14, 2025, 11:24:14 AM »

So now ive managed to sell some bbp and if i do
exec getassetbalance DOGE

I have a balance i dont seem to be able to buy back now, it says my balance is 0.

I do not know what you mean; you would have to start over and write all the tx's down, with their respective debits and credits and addresses.
The amount should be in either your DOGE,BBP, or Wrapped DOGE balance though (it should not be possible to be missing).
You can go through all your tx's in the tx history to see what you traded by double clicking and reading the XML.

141

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 14, 2025, 11:21:06 AM »

exec getdogebalance works every time now

the exchange is populated

i attempted to buy all open sell orders and was able to but my exec getassetbalance DOGE only was deducted from twice... i still have over 6 but spent more than that... i have all the bbp

https://chainz.cryptoid.info/bbp/address.dws?BG39CtdNTZHRt2tcQ83Qqdkv6EE2Q3Xm8v.htm

https://chainz.cryptoid.info/bbp/block.dws?564829.htm

idk what im looking at

As you said above when you buy or sell in the trading room, it only affects your wrapped DOGE (IE getassetbalance doge) balance, but only when a fill occurs.
This way you can have standing orders as long as your balance is greater than the sum of the standing orders.
This allows them to fill when you are offline.

For orders that fill when you are offline, the trades still occur and your wrapped balance is subtracted atomically with the other traders tx - even when offline.

However, if a traders wrapped DOGE cannot pay for the order in the orderbook, the order is automatically canceled, so no trades can occur where users do not have funds to cover them (they will be skipped then canceled right away).

So your balances should reflect what was "transacted" up to this point.

142

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 14, 2025, 11:17:21 AM »

Hi again Rob !

Here are the two TRADING-ASSET-DOGE addresses I see in my wallet:

B98GozkCagidcdFMY2zyKf7k3ioud2DgZz
BM9NqJq4JEDcGuEa1oR3vcpKgLPaoeDgzz

Yeah its weird because I havent seen that happen to any of my 3 installs (it may be a race condition).
Can you tell me exactly what is the label on each of them?  "TRADING-ASSET-DOGE"?  Yeah, they were both mined as DGZZ DOGE asset addresses so they are valid.  Technically the wallet should work fine with two of those.  I will add code very soon to show the address in 'exec getassetbalance' that goes along with the amount.

143

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 10, 2025, 03:33:32 PM »

Hi Guys!

Sorry, late in the game - hectic these days. I just downloaded 0.22.9 and here is what I have seen so far:

- Exchange showed up fine, populated.
- TRADING-PUBLIC-KEY and TRADING-ASSET-DOGE all there without hassle, cool. For some reason I have 2 addresses labelled TRADING-ASSET-DOGE, don't know if that is normal.
- I transferred some BBP to my TRADING-PUBLIC-KEY
- Checked the board: SELL @ 0.00002939 and BUY @ 0.00002700
- Placed a SELL order for 1000 BBP @ 0.00002900, showed up fine (received warning that min order size is 1000 BBP when tried with lower amount)
- Placed another SELL order for 1000 BBP @ 0.00002700 (where the best BUY was at) : My order just got listed without execution. I understand the book only executes matching orders; so was not surprised to see my order not get executed. Still, kind of awkward to see SELL @ 0.00002700 and BUY @ 0.00002700 on the book
- Placed another SELL order for 14777 BBP @ 0.00002700 (to match a standing BUY order on the book) : executed fine, and the BUY order was deleted from the book.
- Cancelled my non-matching SELL order @ 0.00002700 : deleted from the book, good.
- Attempted to mess the book buy placing a non-matching SELL order @ 0.00002600 under the price of the best BUY order @ 0.00002700 : OMG it is listed

I think we need to be able to prevent that from happening, until exact matching requirement is lifted.

I will keep playing around and let you know if I come across other glitches. But, all in all, it is WONDERFUL to see this capability in the wallet. Thanks a lot Rob !

Ahh, thanks for testing and the compliments, sweet!
Notice that I did take into consideration the ability to list another ticker in the future.  Most of the plumbing is there.

I havent dug in to your details too far yet: but notice that when you place an order that matches another order and both are your own (IE the flags are M and M) there is an area of the code where it either cancels both automatically, or ignores them (cant remember which one it is) because it results in an unfillable atomic tx, so that may explain that one exception above.  But yeah everything else should be the "real deal". 

I am going to work on fractional fills soon as that would be exciting to get in there.

Glad we did it, as it provides some value to BBP (rather than just another clone coin); plus Bololex has not come back. 

So im just reading through your message Talisman and on the two addresses for TRADING-ASSET-DOGE, can you paste the pubkeys?  I just want to see if they both end in DGZZ.  That is weird, because we check to see if you have one before we mine a new one.   It should be OK though as when the wallet goes to spend a colored coin, it searches all the DGZZ addresses for it (IE the same type of coin that is being spent in the trading room).  Need to make it so it lists the pubkey on the 'getassetbalance doge' output as well (TODO).

Very cool on the test results, they seem OK.  Now I will get on to fractional fills soon.  When fractional fills work, there will no longer be crosses in the order book.

144

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 10, 2025, 03:30:35 PM »

Looks like it has now been solved. Maybe just a suggestion maybe have the amount of BBP and Doge available for trade on the exchange page.

Ahhh,  great to see that solved it, Praise God!

Yes, good idea, notice I left an area available for metrics.  I also left a little line in between the Bid and Ask where we can put in the current Midpoint (IE the current price).

- Add some volume, price and metrics to the top right and mid pane
- Implement Fractional fills would be sweet

145

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 08, 2025, 10:48:11 AM »

BIBLEPAY 0.22.9 - Mandatory Upgrade

- Add stability to exchange RPC functions.

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

All, please upgrade to the latest version (available on the github link above).
Now theoretically all of the commands should be stable.
Aids, can you please check your 'getdogebalance' is stable 7 times in a row during a retest?
And now, Prof Budinga, you can try checking the Exchange room stays populated.
Note that anyone who has an encrypted wallet, you do have to unlock the wallet for the exchange to function.
There is still a 2minute delay after booting the wallet (for the exchange to populate); once that expires it repopulates as you move the mouse over the grids.

146

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 08, 2025, 09:47:46 AM »

Hi All!

So I believe I found the problem.
I'm testing the solution now.

We should have an update very soon.

147

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

« on: February 08, 2025, 09:43:43 AM »

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.

148

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 04, 2025, 07:20:12 PM »

Ahh, thank you for the screenshots.
Actually its really good to see that you both had the same problem, because ironically I have not had it from my VM or my home pc.

Its possible that I fixed something that did not get in the latest release; really busy at work, so Im going to have to try to reproduce this on my laptop which is not using the compiled version.

Give me a couple days for things to settle down and ill be back asap.

PS In theory you do not have to list orderbook or create atomic from command line (command line should only be needed for the exec getdogebalance etc).  Aids_S,  out of curiosity, on those instances where you had a 0 return for getdogebalance, were those after spends or were they just random problems?  (Cause that should only happen after a spend). 

PS II:  One other thing can you both try in the mean time:  There is a timer meant to save resources, inside the Exchange page inside the order book grid.
It goes to sleep once every few mins and only wakes up if there is mouse move Over the top or bottom grid.  Try this, after the orderbook goes blank (and after 2+ mins after a cold boot) click around in the grid area and wait a few secs and see if that fixes it? 

149

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: February 03, 2025, 11:27:43 AM »

Hi Rob,

100% i am on the right version but my trading room is blank, please see attached image. The error is unable to create atomic tx.

Thanks

Its not normal at all, so we start with a few questions.
1) If on windows, try to go into this folder and delete this file :
%appdata%\Biblepay\SAN
Delete the sidechain file.
Then stop the node and restart the node.

Wait more than 2 minutes then see if the exchange room is populated (there are something like 10 orders in there).
It does stay blank the first 2 minutes normally.

If it still happens, please paste a screenshot of the error.

2) When you go to Window | Receiving addresses, and search by Trading, do you have both a Trading-public-key and a Trading-asset-doge populated?

150

Active Discussions / Re: BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

« on: January 31, 2025, 02:17:21 PM »

I will say the majority of the time exec getdogebalance returns 0 even though the balance is 7.3

then exec wrap doge returns this

14:03:37
exec wrap DOGE 5


14:03:37
{
  "Command": "wrap",
  "id": "0",
  "Tx": "{\"SymbolBuy\":\"\",\"SymbolSell\":\"\",\"Action\":\"\",\"id\":\"0\",\"Version\":1,\"Quantity\":0,\"Price\":0,\"Status\":\"NA\",\"Signer\":\"\",\"Signature\":\"\",\"CollateralBBPAddress\":\"\",\"CollateralDOGEAddress\":\"\",\"CollateralALTAddress\":\"\",\"CollateralAssetAddress\":\"\",\"CollateralTXID\":\"\",\"ReturnTXID\":\"\",\"BlockExplorerURL\":\"\",\"Message\":\"\",\"AltAddress\":\"\",\"TXID\":\"\",\"MatchedTo\":\"\",\"FilledQuantity\":0,\"Time\":1738350217,\"Height\":0,\"Error\":\"\"}\n",
  "Error": ""
}


or am I missing steps?

1) I have not had that problem where getdogebalance returns 0 most of the time, however I think I know what it may be.
The only time getdogebalance is 0, should be after you spend the doge on an unconfirmed tx for 1 block.
Fortunately, once you wrap the DOGE into BBP-DOGE, you do not have to use the "real" DOGE again, so that problem will be minimalized.
Try this, if you go to your BBP Doge address on blockcypher:
https://live.blockcypher.com/doge/address/DSb6QT7eEsMLFgL4vzPKTBqgQnqEDLPmGE/
Whenever you have an unconfirmed tx, you may see the 0 balance.
If you have everything confirmed, you should see the right balance.
Wait for that to be stable before moving to the WRAP step.
2) Now do the exec wrap command and it should wrap.
Once you wrap, dont do any more DOGE wraps until your balance is > 1 confirm again (or you may see the 0).

3) You can then do this:
exec getassetbalance doge
And now see the total of your wrapped address (the DOGE is either in one place or another, but never missing).