Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 128. (Read 243386 times)

I did send my available balance to my account before rebuilding... :/ hmmm..

Also stupid question, but what does ABN mean?

Well, when ABN first popped online there was a fork that I ended up mining 14k into a wallet, and then I buggered some things up and had to launch a backup of my wallet.dat, erasing the 13k I saw on that chain/wallet(my main had a lot more in it so I panicked a little.) Could have tried sending it to myself but I didn't even think about it.

Thanks again, that's really kind of you. Smiley I also may be a guy who reads into things people say (such as yourself) a little more thoroughly than others -- so I get what you are saying. I think =P haha

Not a problem, it has been sent. When your wallet fully resyncs you should see it pop in.

There's a chance I blew a good amount when I accidently mined a fork / solo mined 3 blocks by myself once... Maybe it wasn't on the fork. o.O

I hope I can keep them somehow, some of the txs I tested are showing as I rebuild index.

I'll definitely let you know.

And wow, here's a key, thank you very much!

B5D3KtJmeERVF1JEtJTMLkxcGAV4a2p8Wx

With my experience I didn't get to keep any of my forked coins, unfortunately. It gets replaced with original coins mined previously once you re-sync.

I'll tell you what, though. Post a recieving key for me and I'll send you a little something for your work on Twitter // and showing me into this.

Thank you!

EDIT: that spacing is so specific. I will hold onto said fork coins hopefully

1.linux  ./biblepayd -daemon -reindex
2.win    in wallet TOOLS-WALLET REPAIRS-REBUILD INDEX

 

Can you please help me resync? I would like to do it right. Just need a step by step?

Your version 1.4.3.3 is OK, so you don't have to upgrade yet (if you do upgrade please wait til tomorrow as we have 1440 coming out tonight).

Best bet in your case is to resync.  Your chain is too short.  Its most likely due to what started a few superblocks ago (with our prior version sancs not upgrading) around the time ABN came out the first time (around block 127000).

Sorry for the inconvenience, but you probably mined some coins on a fork.

Thank you for the response. Just ran reconsiderblock got this

I think your on the light chain though, first can you please tell me what this results in:
getblockhash 129815

(The reason I say I think you are on the light chain, your diff in the paste above is only .50, but, unfortunately it should be over 5000).

If you are on the wrong chain you have to run the reconsiderblock command from the previous page (or resync from 0).

My wallet isn't sending coins through to COINEXCHANGE... They show up confirmed in my wallet, but also these aren't showing up on either block explorer.  What I've read so far from the past few days led me to understand/witness:

1. There is a light chain and a heavy chain.
2. CX and SX are both on the "heavy" chain.
3. The heavy chain as of me typing this was just at around block 129846.
4. A problem occurred at block 129785.
5. I am using the biblepayevo64.exe wallet and have updated since mandatory.  (My version is 1.4.3.3)
6. My mining is fine. I began mining in March using purepool and have also used 1-click mining configuration since upgrading to 1.4.3.3.
7. To get my coins from the old Biblepay Core wallet I downloaded in March I moved "wallet.dat" over to my BiblepayEvolution folder in "Roaming" [using Windows 10, obviously]
8. Around a month ago, purepool stopped paying out mining payments to my wallet.
9. I've been mining successfully with my coins confirming after 102 blocks since setting up 1-click mining configuration in this wallet (1.4.3.3).
10. None of my transactions are showing on either block explorer, even though nodes are confirming both my mining and test transactions (1 to myself within the QT wallet, 1 out to Coinexchange.io)...
11. My wallet has worked fine before. I was able to send coins to a Breadwallet I installed for Biblepay on my iPhone in June the day it came out.
12. I've previously seen transactions on explorers for my coins... however none of my addresses are showing in addition to the transactions or blocks (which have confirmed).

Here is my information from the Console (showing that my wallet from the biblepay.org website "biblepayevo64.exe" and version 1.4.3.3 is behind where some of you are blocks wise):


If the error is because of the software version I am running can you please kindly explain how to upgrade to the latest?  I haven't updated because its been busy for me to keep updated with work life and other things and I figured since I had done the mandatory update to evo and even updated to a newer version than 1.4.3.1 I was running a valid wallet.

Blocks are behind but everything is working as far as confirmations and receiving coins. I am having trouble getting coins to the one exchange I tried CX. I am still mining the "main" chain apparently but blocks are lagging when I look in the console (essentially "blocks on the explorer are showing up faster than being recognized in my wallet").

Any ideas what to do? I'd hate to lose these coins as I am a huge believer in this project and thankful for what you guys are doing for people like me by creating something this amazing.

I will let you know if coins show up in my CX account.  Thanks again and sorry if I messed anything up?

Edit, this is the confirmed CX deposit I tried to make but it won't show at CX:

You were right, the null did work and my blockhash went to the correct one.

Its temporarily off to allow us to build a heavy chain.  We can turn it back on tomorrow morning once things are stable.

That means it was successful, but please check your 129815 hash now.

** PLAN OF ACTION TO MAKE BIBLEPAY ROCK SOLID **


It feels like ever since I said we would be "rock solid" a few days ago, and that "stable-prod" is one of our new features for Evo, the Devil has come and tested the wallet (by trying to steal, kill or destroy).

I just want everyone to know I am 100% committed to making BiblePay stable and secure in prod, and permanently fork free.  We've completed a lot of development work to this end, but certain circumstances have tested us.  The bottom line is we need a sanctuary code upgrade to complete two of our features that enable stable-prod and fork-free to actually work.

First of all let me explain the order of events and why people had to issue the reconsiderblock command above.

During block 129785 (today's generic smart contract superblock), the sanctuaries tried to break a business logic rule.  This caused our daily GSC *not to emit*.  (We missed today's GSC and the BBP has been burned).  Due to a feature in the Dash-Evo codebase, once a block is marked as 'invalid', even if the lead devs come to the rescue, and attempt to replay the block, the nodes that are online will never accept that block (unless they type the reconsiderblock command in above manually).  Since our heavy chain has that block in it, it was necessary for us to ask anyone affected to intervene by manually typing the command.  The second problem that occurred today, is BiblePay has a feature to allow the devs to create a hint for the wallet to overcome this situation, but it failed.

So, in light of this, I am creating a plan of action that will mitigate this scenario permanently.  Note that technically since we have clearly identified the reason for the formation of this fork (its root was at the GSC height) this was technically not a fault of ABN, not a fault of POBH, but it was a purely a fault in the GSC POG business rules.

Plan of action to mitigate this issue permanently:

1.  Rob will identify the root cause of the POG business rule that caused one entry in the superblock contract to attempt to pay too much (this will fix the issue so that the superblock will payout tomorrow).
2.  Rob will identify the reason our devs could not issue an emergency hint, and we will fix the feature (this enables the fork-free and stable-prod features in prod).
3.  Sanctuaries will need to upgrade to this greater protocol version tonight.
4.  Regular users will not be impacted, and will not be required to upgrade.

             


When use reconsiderblock in the RPC/debug, it returns with "null"

Edit: the blockhash for 129815 returned to 85f39c01a397afcdb744e170d8decb0dd90f2e6473f0f31da8e1456105557aa9

what happens to abn?
  "required_abn_weight": 0

Found that the Linux version seems to require a reboot but Windows does not. Just an FYI to others.