Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hi Rob,
exec getassetbalance trading shows i have loads in it, but when i go to coin control the trading public key shows 1bbp. I just sent another 100k coins to see if it goes up.
Ill give it an hour or so, and see.
Hi Bro Budinga,
Can you give me an example or a paste of what output you mean?
Im not sure what you mean.
Heres two things you can try:
1) exec getassetbalance trading
Verify balance is good (^ that command only works on the latest version of the wallet btw).
2) From coin control, find your 'TRADING-PUBLIC-KEY' and verify it has a positive balance.
You may have spent some from it, if so you can just re-send funds to it.
Then you can LOCK the funds with Coin Control to keep that from happening again.
The exchange can spend from it when an order is filled.
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
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.
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?
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?
Thanks bro.
Just double checking, are you definitely on v0.22.8?
And you are in this Exchange trading room (see pic) right?
If so what is the exact error message?
We moved to the UI version.
PS Try downloading it from the Github link above; our biblepay.org probably takes 24 more hours to uncache.
Alright everyone, this release is ready to test.
Let me explain how this works.
1) Wallet will be able to support more than one Asset (IE Trading Room) in the future as the architecture is created.
Right now, we just have DOGE-BBP.
2) There is a trading UI now, click Exchange.
3) On boot, the Exchange will not load for 2 minutes, to keep the wallet boot fast.
4) In order to trade, the wallet needs both a TRADING-PUBLIC-KEY and a TRADING-ASSET-DOGE address.
Each unique trading room we create, we need one corresponding public key for the foreign currency.
Its very easy to fund the BBP side for trading: simply go to receive addresses and copy the TRADING-PUBLIC-KEY and send yourself some BBP and that will allow you to make SELL transactions in the DOGE/BBP room.
However, now that we have a new concept (Assets), your wallet needs to MINE a TRADING-ASSET-DOGE address in the background.
It will do this automatically, but you need to unlock your wallet on boot for it to happen.
Just unlock it and wait 15 mins or so before placing your first trade.
If you place a BUY trade in the exchange room and your wallet has not yet mined the ASSET address, you will see a warning.
5) To send an ASSET from one BBP wallet to another, from the rpc do a :
exec sendasset SYMBOL dest_asset_address amount
Note that you can only send assets to another ASSET address (you would need to set up a second BBP terminal and copy it to the clipboard, as it must end in DGZZ if its a DOGE asset.
6) In order to BUY in the exchange room, you obviously need some wrapped DOGE.
To get that do this:
exec wrap DOGE amount
Note that before you do that, you will need REAL doge, so try:
exec getdogebalance
You can fund your DOGE public key with some DOGE first, then you can wrap the DOGE into BBP-DOGE with the wrap command.
Once you have wrapped DOGE, you can trade in the trading room with it and it does support Instantsend.
7) To Unwrap your doge (I recommend doing this sparingly because it is a heavy process):
unwrap doge amount
The doge will be unwrapped and sent back to your DOGE public key.
Always wait a DOGE block before doing a 'exec getdogebalance'.
8 ) The transaction fees have been lowered by a magnitude in this version so that Wrapped BBP-DOGE will have miniscule fees that will not interfere with a wrap or unwrap.
9) In this first version, only complete MATCH trades will execute. IE:
Sell 9000 BBP for .002 from USER 1
Buy 9000 BBP for .002 from USER 2
Will match and execute.
10) The Flags column in the exchange: M = Mine , T=Theirs
I've got a TODO to create partial fills asap.
Just let me know if Ive forgotten anything.
Good luck!
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 - 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.
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.
Thanks bro Budinga.
Alright, I will post a little list of the final things we need to test and start on those.
One is creating a testnet proposal, and verifying the wallet votes on it and pays it.
Ill post as soon as one is created in testnet.
PS If you want to give me your testnet address, Ill send you some BBP so you can see if instand send works.
Mandatory upgrade for TestNet
Biblepay v0.20.18
Code has been released to github.
Windows is ready for download (see link in op post).
Verify your wallet upgrades to newest version and then start with "-reindex=1".
Sync to block 215583 hash 000015d648efc77ed5f25743c388780fae99307a38aab6efe1f6641e5b7e9a3c.
Let me know if you are synced.
Hi, yeah, I see the problem; although I tested a full resync a few times before the latest release I apparently added some consensus breaking logic later in the development cycle that caused this.
So, Im adding some fixes for this and will need to release a mandatory testnet upgrade to get around this.
Let me do a round of testing with my 3 testnet sancs to ensure we are staying in sync and resyncing first to avoid issues.
Ill post when I have the mandatory upgrade ready. Thanks for testing.