Forum Replies Created
-
AuthorPosts
-
d3vnu77Participantd3vnu77Participant
Trust me, I don’t want to edit your code. Right now I’m just looking at what is happening in it so I better understand it myself. Plus I can tell your a much better coder than myself, lol. Any edits you might see is just me trying to figure out what is happening and help us both. I’m working with a fresh copy of your code now.
Also, I want to let you know I appreciate your help in this. I am at my office for the day today and I’m hoping to get this resolved and thank you for helping me.
So the $txrow->created_time is equal to the correct timestamp as you thought, and can be seen in the screenshots can you insert timestamps directly into a mysql database or do you have to convert them to YYYY-MM-DD HH:MM:SS?
Attachments:
You must be logged in to view attached files.d3vnu77ParticipantModifing the coins.csv had no effect, if I dump the $coin variable in wallets_declare_adapters() it shows that decimals have been set to 10 or 8 or whatever is set in the coins.csv file.
I just re-downloaded the turtle-coin adapter source code and overwrote everything to ensure I made no edits. Reedited the coins.csv to 8 decimals, however when inserted into the database I am still only getting the decimal place to move by 2 places compared to what the RPC is saying.
Mofidying the coin.csv has no effect.
Attachments:
You must be logged in to view attached files.d3vnu77ParticipantThe problem seem to be that when $this->get_decimal_places() is called, it returns 2 instead of 8.
This is because 2 is hard-coded into the get_decimal_places method of the coin-adapter-turtlecoin.php
If I change the hardcoded value to 8, it fixes everything.
d3vnu77Participantthis is what I get if I dump the tx… basically this is suppose to be 1 ARMS, so the decimal is only being taken down by 2… check my screenshots, am I inheriting the turtlecoin decimals when I should be at 8 decimals?
The amount of 100000000.
Should be 1.00000000 (moved 8 decimals over)Digging deeper into the code to figure this out… sorry I’ve been in and out, been busy with my other business.
Attachments:
You must be logged in to view attached files.d3vnu77ParticipantI changed the coin.csv deciaml place from 4 to 10 on ARMS.
Deleted transactions, re-imported and am still getting amounts that are off by 6 decimals… searching through any code I might have added that might have don’t something like this but I don’t think there is.
d3vnu77ParticipantYes, seems created_time is all zeros in the wp_wallets_txs table.
Attachments:
You must be logged in to view attached files.d3vnu77ParticipantOk, so it is on a new wallet, all old transactions are gone. I sent a single 2ACoin (1.0000 ARMS) to the new address and it is still off by 6 decimals. Says I received 1,000,000 ARMS. Going to re-read you solutions before to see if we cant fix this.
I think I am going to not try to import the old wallet and just stick with the new wallet to reduce problems in the future. So now I just have to fix the 6 decimal out of place thing…
Also point out an invalid date showing up on the transaction list.
Attachments:
You must be logged in to view attached files.d3vnu77ParticipantCompletely re-scanned the blockchain, did not import any transactions…
d3vnu77ParticipantI set up an autohotkey script to auto refresh the cron job webpage by pressing F5 every 5 seconds.
After it got to the correct block height that it should have been at > 500000, there is still no transactions entered into the wp_wallets_txs table…
Attachments:
You must be logged in to view attached files.d3vnu77ParticipantOk, after the daemon was running I changed the max-height to 1, now it seems to have started to scan from the bottom.
d3vnu77ParticipantWell, it is not letting me post my full answer. Anyhow, it wouldn’t let me delete my transient with wp-cli…
However I found it in the database _transient_trtl-ARMS-settings-max-height : 692781
I deleted that transient and I also ran “rm -rf wp-content/cache/*”
I restarted the RPC daemon
However the same transient keeps getting generated soon after: _transient_trtl-ARMS-settings-max-height : 692781
d3vnu77ParticipantHmm, not seeming to let me post here.
July 23, 2020 at 2:13 pm in reply to: I’m getting ready to replace my hacked up monero adapter with yours #8947d3vnu77ParticipantUnless there is a faster way to force the scanning of the blocks?
July 23, 2020 at 2:02 pm in reply to: I’m getting ready to replace my hacked up monero adapter with yours #8946d3vnu77ParticipantOk. currently waiting for the blocks to continue scanning. We are to 406000 height at the moment. When it finishes we can check to see if there are still issues.
-
AuthorPosts