So, Rob, I want to draw your attention back to the UTXO stake I did earlier, as I think I may have identified a bug, or it was just some weird glitch for me. Firstly, I put the stake for 1 mil bbp in the actual control window, as you can see, but it says I staked a total of 4.99 something million bbp instead, all of what was in the wallet I sent the stake from. I have no idea why this is, but it does make sense why I was having trouble adding to the UTXO, as I was completely out of tbbp. Also, I did spend the UTXO stake, and, as you pointed out, it burned 50% of the stake as a punishment for taking it out early. I tried withdrawing more that I had, and that was rejected, as well as withdrawing more than my stake altogether. However, maybe you could add a feature where, if someone tries to withdraw from a UTXO stake and the fee would make it so that they have an insufficient balance to finish the transaction, you could say that in the window, so the user knows why they don't have a high enough balance, whenever it might look to some like they do have enough for it to go through. Very easy, and I like the reward/risk factor to it. I did just want to point out, though, that I didn't get the 10 mm you had said you would send so I could keep testing. Not an issue, just letting you know. Also, I am a man . I will be doing my own nft soon, and I already bought one through the command prompt, will try to buy one through the site in a bit. I will also look into testing the BiblePay University quiz feature. Quick side note, when do you think that C# will be implemented? I see that the roadmap puts it at the end of the year, but I know that all of that can shift based on other factors. I am really looking forward to it, and I think that it will really change the way this currency is able to be used.
May God bless,
twinkle
Hello bro. Twinkle (thanks for letting me know), yes, so first on the fact that it consumed all 5MM: This is not a bug, but it is a deficiency in our documentation. When a user does any type of stake, the wallet looks for any coin *above* the min_bbp_amount (and less than 10MM) and tries to use it (and it does display the proposed amount in dry run mode, but like I said its not too intuitive). If a user bankrolls first, then obviously it will be picking coins of more accurate value. It cant pick any arbitrary amount because the nature of a UTXO is 'one unspent output'. Yes we definitely need better docs for that part.
So on the error message, ill add a todo right now to show a better message if the user tries to spend too much from the UI when spending a locked coin.. (I added 4 help messages earlier this morning based on the prior suggestions).
On not getting the tBBP, I sent it to the yqJb* address you posted from your successful utxo stake. Could you do me a favor?
Please run 'getrawtransaction 145db7df6b8a7ea0fa53f6fc8ada2c89a542781b1ae5866c8c50d51622df1f9b 1" and see if you can see the transaction? I want to make sure everyone stays in sync. That is one of your wallet addresses isnt it?
Thats cool you bought an NFT, you should now see the nft in your Owned NFT list.
On c#, I agree, Im very zealous about c#, I used to be a c# programmer for a long time. I would love to make it easier for c# organizations to integrate with the block chain.
As a matter of fact, we have two projects that use c# and move us to completion on that item. I believe once these two are finished, we will have fulfilled the roadmap entry as well. I think, if Im not mistaken and being too optimistic, I still think we might hit the deadline by the end of the year.
First of all, please read project 1, unchained:
This one allows a c# org to host the biblepay.dll on their web server:
https://unchained.biblepay.org/Note that by finishing this, and adding our constitution-protecting and freedom-fighter features located here:
https://forum.biblepay.org/index.php?topic=756.0(And be pre-warned that site is still not ready for comments because of my current derailment on Mac builds and Harvest builds, but it is close),
my point is once that thread is open for testing, theoretically we will fast-track c# development to be 95% complete by the end of the year (hopefully).