[alexg]

Hello,

The users/balances list is now added in version 3.9.0. Please see the release notes here: https://www.dashed-slug.net/static-wallet-shortcodes/

kind regards

[alexg]

Thank you for reporting this. It looks interesting.

I will need to review this more extensively before I can determine if it can actually be helpful.

If so, this will require a new coin adapter to be developed.

with regards

[alexg]

Hello Megan,

This is not currently easy to do.

Actually I am currently working on a big change that will allow shortcodes to do things like that.

First I will roll out these changes to the parent plugin, possibly later today if all goes well, or early within the week.

After that, I will apply similar changes to the Exchange extension. I will try to do this as well.

In any case, the timeframe can be controlled via JavaScript. To set the knockout observable to 1 hour candlesticks, you would do:

wp.wallets.viewModels.walletsExchangeChart.selectedTimeframe('1h');

You could attach this to the wallets_exchange_ready bubbling event, like so:

$( 'html' ).on( 'wallets_exchange_ready', function( event, markets ) {
    wp.wallets.viewModels.walletsExchangeChart.selectedTimeframe('1h');
} );

The available timeframes are: ‘1m’, ‘3m’, ‘5m’, ’15m’, ’30m’, ‘1h’, ‘4h’, ‘1d’, ‘1w’

Hope this helps.

with regards

[alexg]

OK, please tell me the following:

1. You have posted in the block.io adapter section. Are you using the block.io adapter? Have you disabled the built-in Bitcoin core node adapter?

2. Are you still attempting a deposit, or is this a withdrawal attempt? You first mentioned deposits, but then withdaw.

3. Is this a new installation? Or did the balances update previously?

4. Did you use a user deposit address (i.e. an address shown in the [wallets_deposit] shortcode?

5. In the “Wallets” -> “Adapters” screen, does your coin adapter show as “Responding” under “Adapter Status”?

6. In the “Wallets” -> “Adapters” screen again, does the “Hot wallet balance” update?

7. In the “Wallets” -> “Transactions” screen, does your transaction show at all? What is its status?

Please let me know. Thank you.

[alexg]

Hi, I confirmed to use the wallet shortcodes, but the problem is, payment received and withdrawn will never get confirmed. I tried running cron jobs but the problem still persists until now

[alexg]

Hello,

The frontend learns about coin information from your server via the get_coins_info JSON API call. The coin icon is filterable. Please see https://github.com/dashed-slug/wallets/blob/3.8.0/includes/json-api.php#L966 . There is a full example in the documentation on how to hook to this filter, under the heading Frontend -> JSON API filters -> Coin icon.

with regards

[alexg]

Thank you for providing this additional info. The situation is this:

The Monero coin adapter relies heavily on the subaddresses feature which was introduced in Monero, but is not available in vanilla Cryptonote. Therefore, the coin adapter will only work with forks that have subaddresses. This includes many, but not all Cryptonote wallets.

Unfortunately you will not be able to use karbowanec wallet with this coin adapter at this time.

with regards

[alexg]

Sure Alex, I know you are busy.

So I did a little bit of investigation and found out that some cryptonote based wallets such as Karbowanec and Elya does not have the “get_accounts” rpc command.

How can I replace/fix this?

These are the RPC commands available on Karbowanec (https://github.com/seredat/karbowanec/wiki/RPC-Wallet-API)

Reset
Get status
Save
Get view key
Get spend keys
Get addresses
Create address
Delete address
Get balance
Get block hashes
Get transaction hashes
Get transactions
Get unconfirmed transaction hashes
Get transaction
Send transaction
Get status
Estimate fusion
Send fusion transaction
Validate address

[alexg]

No, unfortunately I am not able to work on this at the moment.

To be clear, this will not be very soon, because I am busy with other tasks related to the plugin.

with regards

[alexg]

Any updates on this issue please? we need to decide if this plugin is the best suit for our business atm.

[alexg]

Thanks I will look at that plugin.

The settings do not have to be the same. Each type of cron trigger can have its own interval.

with regards

[alexg]

Hello,

No, actually there should not be any problem with running multiple cron jobs, both initiated from the WordPress wp_cron and from the system (server) crontab.

If incoming deposits and internal transactions are processed, then this means that your system is set up correctly.

Can I ask, what is the “WP Cron events dashboard”? Is this from some cron-related plugin? Let me know which one and I will have a look.

thanks

with regards

[alexg]

Yes, I understand.

The question actually is not which files to modify:

You should never modify code in a plugin or theme. Whatever changes you do get overwritten on each update. Instead, use the hooks (actions and filters) provided. In this case, simply start a new plugin file, then hook into the wallets_transaction action.

This will let you intercept all transactions that are discovered by the plugin. This way you can handle them any way you like, without having to communicate with the wallet directly. So, to intercept incoming transaction IDs for coin XYZ you’d do something like:

function handle_transactions( $txid ) {
   error_log( $txid );
   // handle the txid any way you like
   // you would typically request the transaction data here from a wallet or block explorer
   // then, maybe store the data to the db, or send an email using wp_mail()
}
add_action( 'wallets_notify_wallet_XYZ', 'handle_transactions' );

Hope this helps.

with regards

[alexg]

Thanks.

Writing the transaction to the DB would involve a new table, for the reasons discussed above. The wp_wallets_txs table is for user transactions.

If you are planning to create a plugin to handle and report stake rewards, it is best if you create your own table or structure to store this info.

You can use the existing actions to intercept incoming TXIDs, or use your own mechanism altogether. In any case, this feature is out of scope of this plugin.

with regards

[alexg]

Hello,

You are correct. The created_time field is shown, while the updated_time field might be more helpful.

This will go into the next patch release.

with regards

[Author]

Posts