Bible Pay

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.


Messages - sntjo2847

Pages: 1 2 [3] 4
31
I agree, the lime and black is much more consistent for the site; I reverted it back.
Great! Thank you, it is much nicer to look at now.

32
Well the signifigance of Maroon and Gold is 'The blood of Jesus' and the breastplate of righteousness; but the answer to your question is I'm standardizing the CSS so we have less colors all over the place, so I combined the tables yesterday to be one color.

I do like Green but I also need to make sure we have as few colors as possible in the theme.
Ah ok, good to know it does not mean something bad happened.

While I understand the reason for the color by significance now, the Maroon and Gold is much harsher on the eyes (for me, possibly others too), than the green and black.

33
NFT ca03ff883fb82c28046281786740865769e5795c5ed169b1a7bc155d03549a41 - When the World Stood Still
a8dbf30e-2817-40f8-8597-706d6b18fc13
7/3/2021 5:32:26 AM
-55000
279802

NFT ca03ff883fb82c28046281786740865769e5795c5ed169b1a7bc155d03549a41 - When the World Stood Still
8860de9c-9f7d-4ca0-87c2-75bb387c690d
7/1/2021 12:21:28 PM
-55000
279513
Hi Rob, The block 279802 seems to be the point where an issue has appeared. The block on bbp explorer does not match the block shown through my wallet (1.6.2.8 ). All blocks before match, all blocks after do not match.

34
What is the significance of the background color on the block history page for the pools? They have always been green when I looked, but now it is red on the foundation pool.

35
To add to this:
It looks like the api provider BiblePay uses (blockchair) supports Bech32 format addresses just like the other addresses. So theoretically it should fix it by changing the length check in rpcpog ValidateAddress3.
Notes:
Bech32 address is variable in length, so it should not be checked against a static number. Instead it should be checked against min/max length, as well as starting with the correct prefix.
Note that it appears that LTC also supports Bech32. These have a different prefix than bitcoin Bech32 prefixes.

36
I had no problems creating a BBP only stake.  Thanks for the referral reward, Rob!

Now I'm trying to create a BTC stake, but when I paste the BTC address I copied from Trust Wallet, bc1q08tkcyac8dzwm5wzxacy898g2fu69nsj2kf7fc, Portfolio Builder says "Address invalid." when I click on either "Submit" or "Query UTXO."  Why isn't this working for me?
My guess is that it is because it is because that is a Bech32 format address, which I think is not as widely supported. That is in contrast to P2SH or the (legacy) P2PKH, which are 34 characters long. Bech32 is longer, and there is more than one option for length.

I just checked and it looks like the code checks for the BTC address to be 34 characters long, and gives an Address Invalid error message if it is not.

37
Hi there!

I went to that page, which says :

"Now you can create a Portfolio Builder position from the UI. Navigate to Misc | Portfolio Builder. Realize there are two types of positions: BBP, called native, and non-bbp (called foreign).

To create a biblepay only position, simply choose BBP from the drop down and enter the amount you would like to allocate. This is an internal transfer and the BBP will not actually be spent, it will just be moved to your "UTXO-RETIREMENT-ACCOUNT" internally, and locked."

I did exactly that, and does not work for me.
Ok, so you tried the Portfolio Builder. I will have to leave it to other people who have used it already, since I do not have things transferred to set it up yet.

38
1)  Yes, correct.  Type in 'listutxostakes 0' (these are your stakes).  If you are underfunded on a BTC position, your "coverage" ratio will be for example ".50" if you are only 50% covered.  When you increase your BBP, we automatically reallocate the coverage percent.

2) I was actually providing a solution for you (when I said ' the fee is virtually nothing ' I didnt mean to imply that 100 is a low fee, I meant it in a way that The fee Has not changed from 0 to 100 bbp, It is still below 5 bbp),  the solution I posted earlier asks you to delete a file and reboot.  That fixes the problem (as we dont charge 100 bbp).  Its not a coding error--  Its a FEE ESTIMATE ERROR....

3) Btw, guys, you don't have to do the exec bankroll in this new version.  When you send from the portfolio builder we do everything automatically.  That part needs taken out of the docs.  I suppose its still good to know of though, because some people have quite a fragmented wallet (full of lots of small coins).

1) Wonderful!

2) Sorry if I misunderstood since I did not see the number with anything that said estimate. I shutdown the wallet and deleted the file you mentioned. The transaction details says 100bbp fee, both on my wallet and the biblepay explorer. I will send you a PM with the transaction ID.

3) Good to make sure everyone knows that it is not necessary for portfolio builder. I did know, I only ran it to see if it still worked since someone else on discord said it was not working for them.

39
Hi Rob!

I noticed only today that we have to repeat the utxo stakes under the new wallet (been away for a while), and downloaded 1.6.2.5 to do so.

I am not sure if "https://wiki.biblepay.org/UTXO_Mining" is the latest guide, since the commands mentioned there (easybbpstake and highriskbbpstake) return "method not found".

Tried to stake (BBP only) on the Portfolio Builder, but it keeps saying "Unable to Create Transaction". I understand we do not need small bills any more for the UTXO stake fee, but created some 500-800 BBP bills just to make sure. Still no luck.

Any ideas on what I might  be doing wrong?
Hi Talisman,

Did you notice the notice at the top of the wiki page you linked? It says:
Quote
UTXO has been upgraded and rebranded as Portfolio Builder as of June 23, 2021. This page is only for historical reference.
See 1.6.2.4 Mandatory Upgrade Changes
Portfolio_Builder

40
1) You can cirumvent the Portfolio Builder save fee if you already have a position.  You can send BBP to your "UTXO-RETIREMENT-ACCOUNT" address using the normal wallet send, as long as you ensure the tx amount has the PIN suffix, then it will be found by the sancs and accumulated.

2) The fee is still virtually nothing; please exit the wallet, then erase the fee_estimates.dat file in your datadir, then restart the wallet, and it should calculate correctly.
1) Just to be sure. So if I already have a position like Portfolio B on the wiki page with $100 BBP + $10000 BTC that is working, just quite underfunded on the BBP side. I can then just send $5000 BBP to my "UTXO-RETIREMENT-ACCOUNT" address and it will start accumulating the rewards on $5100 of BBP and BTC instead of $100?

2) Yes, 100bbp is a small amount. I brought it up because something needed fixed, either the code or the help message. I was not referring to an estimate, but to the help message for bankroll, which is in the code at rcpevo.ccp line 2155

41
1. I have a question about Portfolio Builder. Using the Portfolio B from https://wiki.biblepay.org/Portfolio_Builder as an example.
Since this position is deficient in BBP, is there a way to add to the BBP balance (without redoing it completely and having to retransfer assets).
Perhaps something like move more BBP to UTXO-RETIREMENT-ACCOUNT to make up the deficit?

2. I am not sure if this change was intentional and the help message was not updated yet or if it is a bug.
Someone on discord was having difficulty with bankroll, so I looked at the help and saw it was free. Then I tried it out to verify that it works on 1.6.2.5-Harvest. I was surprised to find that it seems to cost 100bbp now.

42
First let me clarify Trust Wallet vs. Light wallets:  You *can* still use our portfolio builder along with a light wallet and create a position, as long as the amount suffix matches the BBP pin, yes.  The idea with Trust Wallet is to additionally bring biblepay a facility to store an entire portfolio in one place, provide a cryptocurrency index for our users (that match the prices on those 10 currencies in Trust Wallet), and as a starting point to "bring in" more future 'vetted' currencies directly from trust wallet (assuming that they add their currencies to trustwallet based on very popular demand).

So yes you can do both.  If I could ask you and others here in the community to gather the top 5-10 difficulties with portfolio builder then I can go ahead and write a dedicated wiki page for trust wallet.  For now we don't have a dedicated doc for it, Im here to help answer questions until we establish some positions and I will take a stab at creating one soon.
Ok, if I understand correctly, then there is no integration with Trust Wallet currently. It just is the recommended wallet to use as it supports many blockchains. I would agree with that as I like Trust Wallet.

One thing with the Portfolio Builder so far:
It looks like the minimum you can add is 5,000 BBP, which is a 10% fee. Maybe that could be a % with a max of 500 BBP? Like 1%, so 5,000 BBP would be 50 BBP fee, 10,000 BBP would have a 100 BBP fee, etc. Then the fee would max out at 500 BBP when adding 50,000 BBP. Just a thought.

43
Hi Rob,

Ah ok, that explains it. Thank you.

I put a notice at the top of the wiki PODC, PODC Setup, DWS pages about them being disabled so it does not cause confusion for new users. And the UTXO Mining page about Portfolio Builder. The Main wiki page needs updated with new Block reward, remove exchanges that are not recommended, etc. I do not have access to update it. Same with pages on the website.

Blessings,
Jo

Hi Jo--

On #2, the problem with that method is you are making the assumption that if everyone is ready to upgrade in the future block, that everything will go well on that particular day.  I chose to start the upgrade as soon as we were in maintenance, in case we needed another emergency update in between.  Without causing any arguments over this, the real deal killer was that our classic chain was already in dip3 mode, and no new pool blocks could be mined in the pool unless they were upgraded FIRST.  That set an extraordinary problem ahead of us meaning we had to upgrade both pools first in order to mine, and in order to mine new clients already had to be running (as users).  So no, dash would not have had this problem because they were not in dip3 mode when they upgraded. 

Ill be back..

44
Hi Rob,

2) That would seem like a reason it had to be on a DM block, which could have been set to a DM block 1 week away, which would allow everyone to update in the meantime. I may be missing something though.
3) Thank you, I realized that after the wallet finished updating. The blockchain explorer is apparently not updated, so it was not showing there.
4) Where would I see such messages? I did not see any message, and there are none in the My Messages tab. I am subscribed to the update emails.
5) Glad to hear such a short upgrade time window is not the norm. I think though that the more stable blockchains normally have longer than 1 week though.
6) I would suggest that if there is a mandatory upgrade it should be posted to github immediately. If it needs another update due to an issue, it can be updated.

Is there a guide to the trust wallet integration? It is not clear how to set it up. I found Portfolio Builder, which mentions Trust wallet integration, but then says you can use any wallet, which is how it was before the update.

Regarding the press release: I think it is a great idea to have a press release. However, the website/wiki should be updated before it is released in order for it to be effective. That way new users are not turned away by confusing/conflicting information. As it stands now, the press release points you to the post about the update, which does not explain how it works. The website does not have the information either, and still points to DWS which was disabled a while ago. And PODC, which was disabled even further ago. I know I spent many hours trying to get PODC working only to discover it was disabled.

I hope my comments / suggestions are not taken the wrong way. I like BiblePay and think you have spent a lot of time improving it. I am especially looking forward to the wallet integration. I want BiblePay to be successful and think that the new user experience is currently a significant hinderance.

Blessings,
Jo

45
BiblePay Core Wallet
1.6.2.4 - Mandatory Upgrade for Entire Network at height 278014


Hi Rob,

These seem like a lot of really useful upgrades. Thank you for all the hard work you have put into it!

May I ask though why this upgrade needed to be done in such a rushed manner? World breaking changes should have more time given to upgrade unless there is a very good reason why it has to be done right away. It seems like this could have been set to a block height that was more than 1 day away. I am not able to check the forum every single day.

Also, there is no build posted on github. And no email was sent out about the mandatory rush upgrade.

Blessings,
Jo

Pages: 1 2 [3] 4