Forum Replies Created
-
AuthorPosts
-
tanger
ParticipantTested and working. Thank you.
tanger
Participantthe database was not imported through the tool. I did rescan the xmr wallet preceding this issue. But I’m not sure if they are related. I successfully performed a withdraw using the same steps as described before your latest update. But I’m not sure if that is related to my issue.
tanger
Participant| xx_wallets_txs | CREATE TABLE
xx_wallets_txs` (
id
int(10) unsigned NOT NULL AUTO_INCREMENT,
blog_id
bigint(20) NOT NULL DEFAULT ‘1’ COMMENT ‘useful in multisite installs only if plugin is not network activated’,
category
enum(‘deposit’,’move’,’withdraw’,’trade’) NOT NULL COMMENT ‘type of transaction’,
tags
varchar(255) NOT NULL DEFAULT ” COMMENT ‘space separated list of tags, slugs, etc that further describe the type of transaction’,
account
bigint(20) unsigned NOT NULL COMMENT ‘xx_users.ID’,
other_account
bigint(20) unsigned DEFAULT NULL COMMENT ‘xx_users.ID when category==move’,
address
varchar(120) NOT NULL DEFAULT ” COMMENT ‘blockchain address when category==deposit or category==withdraw’,
extra
varchar(120) NOT NULL DEFAULT ” COMMENT ‘extra info required by some coins such as XMR’,
txid
varchar(120) DEFAULT NULL COMMENT ‘blockchain transaction id’,
symbol
varchar(10) CHARACTER SET latin1 COLLATE latin1_bin NOT NULL COMMENT ‘coin symbol (e.g. BTC for Bitcoin)’,
amount
decimal(20,10) NOT NULL COMMENT ‘amount plus any fees deducted from account’,
fee
decimal(20,10) NOT NULL DEFAULT ‘0.0000000000’ COMMENT ‘fees deducted from account’,
comment
text COMMENT ‘transaction comment’,
created_time
datetime NOT NULL COMMENT ‘when transaction was entered into the system in GMT’,
updated_time
datetime NOT NULL COMMENT ‘when transaction was last updated in GMT (e.g. for update to confirmations count)’,
confirmations
mediumint(8) unsigned DEFAULT ‘0’ COMMENT ‘amount of confirmations received from blockchain, or null for category IN (move,trade)’,
status
enum(‘unconfirmed’,’pending’,’done’,’failed’,’cancelled’) NOT NULL DEFAULT ‘unconfirmed’ COMMENT ‘state of transaction’,
retries
tinyint(3) unsigned NOT NULL DEFAULT ‘1’ COMMENT ‘retries left before a pending transaction status becomes failed’,
admin_confirm
tinyint(1) NOT NULL DEFAULT ‘0’ COMMENT ‘1 if an admin has confirmed this transaction’,
user_confirm
tinyint(1) NOT NULL DEFAULT ‘0’ COMMENT ‘1 if the user has confirmed this transaction over email’,
nonce
char(32) DEFAULT NULL COMMENT ‘nonce for user to confirm via emailed link’,
PRIMARY KEY (id
),
UNIQUE KEYuq_tx_idx
(txid
,address
,symbol
),
KEYaccount_idx
(account
),
KEYblogid_idx
(blog_id
)
) ENGINE=InnoDB AUTO_INCREMENT=888 DEFAULT CHARSET=latin1 |
`tanger
ParticipantI understand the fixed fee is different from the actual fee charged by the network. But the second transaction shows my fixed fee amount so I suppose it is relevant.
tanger
ParticipantI used the send-to-user form to move .1 xmr to a new user account. No problem.
I sent MAX available .1 xmr from new user wallet to external wallet.
One transaction was sent. Another transaction was created but did not send. See attached images.
Both transaction were assigned same TXID
Fee for successful transaction was: XMR 0.000011180000
I have fixed fee for withdraw set at XMR 0.00001700
One transaction was successful for the correct amount: 0.099983 XMR
I set retry limit to ONE in adapter
I’ve tried withdraw twice with new user accounts with the same result.Attachments:
You must be logged in to view attached files.February 17, 2021 at 6:51 am in reply to: Minimum confirmation adapter setting, and wallet rescan #10003tanger
ParticipantTested and working. Thanks!
February 12, 2021 at 11:54 pm in reply to: Minimum confirmation adapter setting, and wallet rescan #9982tanger
ParticipantThank you. Setting the http timeout to 256 did fix the failed transaction issue.
Outbound XMR transactions are successful and now assigned a TXID in the transaction list, however, confirmation count remains zero on wallets > transaction and user front end.This is only for outbound transactions.
Inbound transactions show correct confirm count.I tried a couple different Monero Daemon connections with no effect on missing confirm count for withdraws at wallet > transactions
Thanks again for your help.
February 12, 2021 at 5:40 pm in reply to: Minimum confirmation adapter setting, and wallet rescan #9979tanger
ParticipantThe withdraw is to a different wallet. Not user-user internal transaction. I’m using latest 17.1.9
additional testing:
Setting retry attempts to 1 – transaction is successful. However adapter sends error: Your withdrawal request has FAILED permanently. (Also tried retry attempts on 2 and 3.)
Last error message:
Could not execute withdrawal: Could not communicate with Monero wallet.
Error 28: Operation timed out after 29999 milliseconds with 0 bytes received.However, the transaction builds and sends through the RPC no problem.
The main issue here: the user balance does not reflect the withdraw, but the funds are sent from the wallet.
I don’t know if this is on XMR side or Adapter side. I’m using latest 17.1.9
February 11, 2021 at 10:15 pm in reply to: Minimum confirmation adapter setting, and wallet rescan #9975tanger
ParticipantI’m sorry for all these words.
I’ve done some additional testing. After selecting Create deposit addresses now for all users on XMR adapter setting.
This fixed the wrong user/address issues.
I was able to send and receive to the wallet.
However, on wallets > transaction page I’m still having issues showing confirmation count on outbound transactions.I’m seeing this occasionally in my monero rpc log:
Error calling gettransactions daemon RPC: r 1, status <error>I don’t know if that’s related to my issue of missing confirm counts on withdraws.
February 11, 2021 at 4:35 pm in reply to: Minimum confirmation adapter setting, and wallet rescan #9974tanger
Participantalso, i want to make it clear that your plugin worked fine until i started messing with things that certainly should never be messed with on a production server. i understand u are planning a major update.
February 11, 2021 at 12:09 pm in reply to: Minimum confirmation adapter setting, and wallet rescan #9970tanger
ParticipantAlso, my XMR adpater is sending funds to the wrong user. If a user requests new xmr address and they send funds to that address, a different user is credited with the funds!
I think I should start over!
February 11, 2021 at 11:40 am in reply to: Minimum confirmation adapter setting, and wallet rescan #9968tanger
ParticipantHello. Thanks for your reply. This is a withdraw XMR transaction. The transaction was successful (the funds showed up on the other end). However, the transaction status reported failed in Wallets > Transactions. When using the JSON API (https://example.com/wallets/api3/notify/XMR/wallet/e0c829f453ca26ba81d21ed96871e85bedf9f83acdc95b10937da2d9526f62c4) returns {“result”:”success”}
1. I can see the transaction in the list as pending until the retry limit is reached and then it goes to fail and no TXID is reported even though the funds did in fact send properly.
2. Going to Adapters page reports the latest top block 2294442
3. Payment ID was not used
Be aware that I’ve been messing with my monero Daemon and monero-wallet-rpc stop, starting, restarting and also canceling transactions on the Wallet > Transactions page. So I’m probably introducing some weird gremlins.
Hope you are staying sane during the global psyop.
tanger
ParticipantThank you!
tanger
ParticipantThanks! My posts now show the Tip login message for new users.
tanger
Participantgreat. thanks!
-
AuthorPosts