BIBLEPAY - DOGE DECENTRALIZED EXCHANGE

To test Portfolio Builder:

Note that we have a new version of BBPExtensions, so after this newest upgrade, click on Extensions.
From that list of Apps, click Portfolio Builder.

The new wallet creates a few new keys:
ASSET-XLM
ASSET-XRP
ASSET-BBP

These are intended to be Portfolio Builder private keys (they never leave the machine and are private to your BBP core wallet).
The idea is when you send assets into these keys, they will be countable by Portfolio Builder (which gives you the ability to earn APR% annual rewards from the PB feature).  The rewards come in the form of Staked Block BBP rewards, which are not enabled yet).

So the way multi wallet works is when you launch PB, the BBP core wallet encrypts these 3 keys and sends them to the multiwallet.  Note the multiwallet runs on your machine in C#, so the keys are never exposed to the outside world.

However, with these 3 keys you can now send and receive XRP/XLM/DOGE from the multiwallet.

The code in the multiwallet is smart enough to create a Stellar or Ripple account if one does not exist.  So this only comes into play if you are sending Stellar from a BBP Stellar wallet to another BBP stellar wallet (we detect that and call the stellar c# code to create the new account).  If you fund Stellar from another stellar account they automatically create the account for you.

For Ripple, the XRP network will create an account for you if you fund the wallet with more than 20 XRP into your BBP Ripple wallet.  That is their network minimum (not ours).  Be careful if you plan on using Ripple, to send it more than 20 XRP to the address so that you don't lose the usability of the address.

In Phase 2, I will add the ability to see the APR% and you assessed staking level, and also to receive the extra rewards.

Hi Rob,

This is great , i am trying to test it now but i keep getting an error please see attached image. My wallet is unlocked and i have tried also as Administrator.

Any ideas?

Thanks

Hi Rob,

This is great , i am trying to test it now but i keep getting an error please see attached image. My wallet is unlocked and i have tried also as Administrator.

Any ideas?

Thanks

Hi Bro Budinga,

Lets try this:
1) Completely close Extensions
2) Unlock wallet in BBP core first from command line
3) Open Extensions, and verify it says PB v1.52 on the list
4) Launch PortfolioBuilder

See if it still does that.  I just ran this on my home PC which had a locked wallet and everything worked.

If it still fails, then do this:
Navigate to %appdata%\biblepay
You should have a pb.dat file, open it and see if there are 4 encrypted keys in there.
Thats what its looking for when it opens.

Most likely it was just the order that you did things (wallet has to be unlocked before launching extensions from the left menu).
Once extensions has that file, then you are good in the future as order no longer matters.

PS :  I just remembered the most likely reason.  You have to be on v0.23.9 for all this to work, as that is the latest version and only that version writes the pb.dat file.  You can actually get PB's latest version, even on old BBP wallets, because the Extensions module self upgrades each submodule, so thats possibly whats going on there.

Hi Bro Budinga,

Lets try this:
1) Completely close Extensions
2) Unlock wallet in BBP core first from command line
3) Open Extensions, and verify it says PB v1.52 on the list
4) Launch PortfolioBuilder

See if it still does that.  I just ran this on my home PC which had a locked wallet and everything worked.

If it still fails, then do this:
Navigate to %appdata%\biblepay
You should have a pb.dat file, open it and see if there are 4 encrypted keys in there.
Thats what its looking for when it opens.

Most likely it was just the order that you did things (wallet has to be unlocked before launching extensions from the left menu).
Once extensions has that file, then you are good in the future as order no longer matters.

PS :  I just remembered the most likely reason.  You have to be on v0.23.9 for all this to work, as that is the latest version and only that version writes the pb.dat file.  You can actually get PB's latest version, even on old BBP wallets, because the Extensions module self upgrades each submodule, so thats possibly whats going on there.

Hi Rob,

how do i unlock from the command line when i use the walletpassphrase command it just returns null, 

Hi Rob,

how do i unlock from the command line when i use the walletpassphrase command it just returns null,

Sorry ignore that last one it does work. But i still get the same error could it be something on my pc blocking it?
I have close - reopened - restarted and i get the same error and also i have the latest client installed.

Sorry ignore that last one it does work. But i still get the same error could it be something on my pc blocking it?
I have close - reopened - restarted and i get the same error and also i have the latest client installed.

When you put in the right phrase, it just returns null meaning "success". 
So that part passed.
Now just go back to the reply and see the question about the pb file, and see whats up with all that part?

When you put in the right phrase, it just returns null meaning "success". 
So that part passed.
Now just go back to the reply and see the question about the pb file, and see whats up with all that part?

I have an ipc.dat file and thats it, and a BMS folder.

I have an ipc.dat file and thats it, and a BMS folder.

I think i solved it. The pb.dat file was in my blockchain folder. I then copied it to the %appdata% biblepay folder and the portfolio builder launched straight away. Maybe something to do with me not using default folders.

I think i solved it. The pb.dat file was in my blockchain folder. I then copied it to the %appdata% biblepay folder and the portfolio builder launched straight away. Maybe something to do with me not using default folders.

Ahh, yeah thats the whole problem.  It assumes the users Biblepay data folder is always at one of three places (Mac,Win,Linux have different defaults).
Its assuming %appdata%\biblepay for windows.
Will have to make a way for the code to respect the custom folder path in our nice-to-have list.

That also explains why your ipc.dat was not being read- which only affects the old behavior when we had a compiled version of unchained for a short period of time.  IPC is used to determine if Unchained was launched successfully so in your case it would just time out.  (No longer used now, however).

Alright let me know how PB works.  I dont forsee any problems with those 3 offline wallets because the code base for each of those is pretty battle hardened.  Stellar released its own version of an SDK (we are using that) and Ripple is very similar: we use its SDK.  Doge is using NBitcoin, same code that runs on unchained when you send or receive BBP.

Ahh, yeah thats the whole problem.  It assumes the users Biblepay data folder is always at one of three places (Mac,Win,Linux have different defaults).
Its assuming %appdata%\biblepay for windows.
Will have to make a way for the code to respect the custom folder path in our nice-to-have list.

That also explains why your ipc.dat was not being read- which only affects the old behavior when we had a compiled version of unchained for a short period of time.  IPC is used to determine if Unchained was launched successfully so in your case it would just time out.  (No longer used now, however).

Alright let me know how PB works.  I dont forsee any problems with those 3 offline wallets because the code base for each of those is pretty battle hardened.  Stellar released its own version of an SDK (we are using that) and Ripple is very similar: we use its SDK.  Doge is using NBitcoin, same code that runs on unchained when you send or receive BBP.

Ill try, now i just have to figure out how to convert the doge i traded on our exchange in to doge in the portfolio builder.

Ill try, now i just have to figure out how to convert the doge i traded on our exchange in to doge in the portfolio builder.

Once you move your colored doge to native doge the PortfolioBuilder DOGE balance should match the 'exec getdogebalance' as its the same key.

Once you move your colored doge to native doge the PortfolioBuilder DOGE balance should match the 'exec getdogebalance' as its the same key.

Sorry Rob one more silly question from me . How exactly do i do that .

Sorry Rob one more silly question from me . How exactly do i do that .

No problem bruvva, just a full end to end example for clarity.
Say a new user wants to move 50 doge to the native doge wallet.
exec getdogebalance
That shows your public doge key.
Send doge there.  After it is more than 1 block do an 'exec getdogebalance' and see the balance has increased (of native doge).


Convert native doge to colored:
Now the user wants to convert 25 doge to colored doge (for trading in the trading room).
exec wrap doge 25
That converts the doge to colored then you can do :
exec getassetbalance doge
Which shows your 25 colored doge balance, while exec getdogebalance now shows 0.

Now you trade for a while and end up with 26 colored doge in 'exec getassetbalance doge'.

To convert back to native doge:
exec unwrap doge 25

Then after that you can do:
exec getdogebalance
And it will be 25 native again.

Also that key will have the same balance as the portfolio builder DOGE key.

PS I will work on portfolio builder rewards next.

No problem bruvva, just a full end to end example for clarity.
Say a new user wants to move 50 doge to the native doge wallet.
exec getdogebalance
That shows your public doge key.
Send doge there.  After it is more than 1 block do an 'exec getdogebalance' and see the balance has increased (of native doge).


Convert native doge to colored:
Now the user wants to convert 25 doge to colored doge (for trading in the trading room).
exec wrap doge 25
That converts the doge to colored then you can do :
exec getassetbalance doge
Which shows your 25 colored doge balance, while exec getdogebalance now shows 0.

Now you trade for a while and end up with 26 colored doge in 'exec getassetbalance doge'.

To convert back to native doge:
exec unwrap doge 25

Then after that you can do:
exec getdogebalance
And it will be 25 native again.

Also that key will have the same balance as the portfolio builder DOGE key.

PS I will work on portfolio builder rewards next.

Fantastic thank you so much, worked like a charm, i enabled rewards in the portfolio builder but i guess ill have to wait for you to work on it.

This is really good work Rob, the fact we do not need an exchange at all is great.

Fantastic thank you so much, worked like a charm, i enabled rewards in the portfolio builder but i guess ill have to wait for you to work on it.

This is really good work Rob, the fact we do not need an exchange at all is great.

Thanks bro, I appreciate the compliment.

Yes, will get this out asap.

Thanks bro, I appreciate the compliment.

Yes, will get this out asap.

I see you already working on it , thanks