[alexg]

Thank you.

wallets6 is a complete redesign from the ground up. It should be ready in a few months™.

Seriously, I have less than 50 dev tasks remaining in my backlog, so, prepare to be amazed before summer, probably!

I think what admins will appreciate the most will be the ability to create and edit transactions and addresses via the admin screens, and the ability to filter transactions by currency, user, tag, wallet, etc.

But there’s tons of improvements under the hood, some of which will eventually allow interoperability with the new Ethereum-like blockchains (account-based rather than UTXO-based).

with regards

[alexg]

Hello,

The plugin should be compatible with 5.9.

The issue with the menu not showing is most likely one that I have encountered before, but I’m not sure under what conditions it arises:

If you have installed and activated the plugin, but you still don’t see the Wallets menu (and admin warning messages), then the most likely problem is that your admin user does not have the “manage_wallets” capability.

Normally, this capability is automatically assigned to admin users and to the Administrator role, when the plugin is first activated. So, try to deactivate and re-activate the plugin.

Some times this fails. You can use any plugin that’s suitable for editing capabilities and assign “manage_wallets” to the Administrator user role. This will resolve the issue. A good plugin for this job is https://wordpress.org/plugins/user-role-editor/

Simply navigate to Users -> User Role Editor and select the “Administrator (administrator)” role. Click on “add capability” and type “manage_wallets”.

If you want to achieve the same via the wp-cli, you can issue the following command in the unix shell of your WordPress server:

wp cap add administrator manage_wallets

Hope this helps.

Please let me know if this didn’t help. If you have any other questions about the plugins please open a new thread.

with regards

[alexg]

Hello,

You can continue using the extensions after your membership finishes (but will not be able to download any new updates or get technical support for the premium extensions).

Apologies if this was not clear. I am currently rewriting the documentation as part of wallets6 development and will add this information in the faq.

with regards

[alexg]

Hello,

This is a straight-forward issue that I can investigate on your system if you like. Can you give me admin access to your WordPress system?

If so, please email me with:

1. link to your site
2. admin login credentials
3. the order_id of one order that you see on the database but not in the API

If you do not want to give me access, then I can guide you to debug this.

Essentially what I would do, is use wp-console to first check if the PHP-API reports the order, and then the JSON-API. Tracing the execution path of the code that handles the JSON-API will make it clear whether stale transients are used, or what is going on in general.

Let me know how you want to proceed.

with regards

[alexg]

Hello,

The exchange only processes standard orders, as with other exchanges. Normally in large exchanges, synchronization with the globally accepted price is done by arbitrage bots.

To have an order that moves with the market, you must create an external script that places an order, then at regular intervals it cancels the order and places another one with the new price. This is what the Exchange’s JSON-API is there for. (In the upcoming wallets6 release, the JSON-API is superseded by a newer RESTful API which is easier to use, but the existing JSON-API will still exist for compatibility with existing scripts.)

Do not simply modify the price of the limit order in the database. The reason that the order must be placed via the API, is that the plugin does checks to see if you have enough available balance.

with regards

[alexg]

Hello and a happy new year to you too!

wallets6 is nearly ready. Last week I finished the online documentation for all components, which is about 60k words long.

I have only 50 tickets remaining, but this means nothing, because:

1. Some tickets have an estimated effort of less than a day, while a few will take me up to a week each.
2. How many days per month I can devote to work varies depending on other things in my life. Usually I manage to work about 15 to 20 days per month.
3. The effort of some development, dev testing, and integration testing tasks is hard to estimate beforehand. Testing can give rise to more tickets as issues are discovered. So it’s impossible to estimate time before actually doing the work.

So I am not in a position to give out any estimates. But it shouldn’t be too many months! My advise to you is to not wait for it, and then when it’s ready you will know, because there will be a RC release on the site, and a blog post announcement, long before I push anything on wordpress.org.

With this release I have decided to not rush things but to do everything properly, as long as it takes. This means that I am way over my initial estimate of 6 months, but I think it’s worth it. Many of the technical debts will be paid all at once when wallets6 is out!

If you follow twitter you will see the announcements.

with regards

[alexg]

Hello,

Thank you, I have received your second email and logged in to check.

There are some JavaScript errors caused by your theme or other plugins, but luckily these do not interfere with the exchange extension.

I attempted to swap 0.0001 BTC for ETH. I entered 0.0001 BTC and clicked the button, to get the error:

Could not place order. Error: Could not enter market order: Order amount must be positive.

This is to be expected. Normally I should be able to see the amount of ETH to receive, but the plugin shows n/a.

Investigating more closely, I see that there is no liquidity on the BTC_ETH market.

This is explained in the Extension’s homepage. The plugin cannot magically import liquidity from other exchanges. There must be an active market to trade currencies.

The [wallets_exchange_market_order] shortcode places market orders. For a market order to execute, there must first be limit orders on the orderbook. Therefore there must be a market maker to place these limit orders around the generally agreed upon price for these currencies.

Also, you should deactivate the ShapeShift extension, because it’s still loading some assets that are not needed.

Please let me know if this is not clear, or if you have any other question.

with regards

[alexg]

@zhak Hello, can you check again? I did not receive any email at info@dashed-slug.net, and I checked my spam folder too.

[alexg]

Hello,

I have added the ShapeShift extension to the list of decommissioned/deprecated plugins, because the platform has shifted to a dex model, and is no longer compatible with the plugin.

It sounds like you’ve done everything correctly. The issue you describe regarding the [wallets_exchange_market_order] shortcode could be due to any number of reasons. You didn’t mention whether there are any errors in the JavaScript console, and whether you have added sufficient liquidity to the market (i.e. limit orders). It could also be due to JSON-API market_summary requests being cached on the server side, or something else entirely.

Are you able to provide me with login credentials so I can check your site myself? If so, please contact me by email. Please send me the link to the page where you use the shortcode, and a username/password so I can check. I don’t think an admin account will be required for this, just a regular user account.

Looking forward to your reply.

with regards

[alexg]

Hello,

I’m not sure why this is the case on your system. I did again some tests on my side and didn’t show any such issue.

Obviously you should disable your faucet, and cancel any wrong faucet transactions for bitcoin, so that your users don’t take away all your Bitcoin!

I am looking to see if there is any possibility for users to have hacked the code to claim a different coin, but I don’t see how this could be done.

1. Have you tried claiming from the faucet? Do you get BTC or XNS when you claim?

2. Did all the users who used the faucet get BTC, or did some get BTC, and others XNS?

Let me know please.

with regards

[alexg]

Hello,

It’s unlikely that the responses are being cached on the client side, since the correct no-cache headers are set in the JSON-API responses.

It sounds as if the JSON-API responses are being cached on the server-side. Did you check your cache or caches? You should be excluding all queries that have the GET parameters __wallets_action and __wallets_exchange_action from your caching plugins. All server-side caching plugins have black lists or exclusion lists. Some “optimization” plugins also do page caching.

(This issue will be resolved once and for all with the upcoming release, where the JSON-API is replaced with WP REST APIs.)

Hope you have a great 2022! Let me know if you can’t resolve this issue.

with regards

[alexg]

Thanks, good to hear that this helped.

Normally I don’t recommend that users edit the code, because any changes are overwritten by subsequent updates to the plugin.

But this is a special case, as the fiat coin adapter will be merged to the parent plugin, as a fiat wallet adapter.

You can rely on the fact that the WordPress text filters will be preserved.

However, the JavaScript validation code will have to be different. Ask me again about this when the time comes to upgrade. It will be very easy to override frontend JS code in the next major version, using the new templates format.

[alexg]

Hello,

Currently it is not possible to disable validation. I have added this option in the upcoming major release.

As a temporary measure, for now, you can do the following:

1. Delete the minified javascript file: wallets-fiat-0.6.3-beta.min.js. This will cause the plugin to fall back to using the unminified version, wallets-fiat.js

2. Edit the wallets-fiat.js file as needed to conform to your validation requirements, if any.

If you change line 116 from:

return val && IBAN.isValid( val ); // check not empty, and valid iban format

to
return val.match( /^\d{9,}$/ );

then this will disable IBAN validation, and will check if the value has at least 9 digits

That’s it! (You can optionally minify the file if you want, but it’s not necessary.)

As a sidenote, if you need to modify the error message for this field, use the wallets_fiat_ui_text_iban_invalid filter, like so:

add_filter( 'wallets_fiat_ui_text_iban_invalid', function( $text ) {
	return 'The number must be at least 9 digits long';
} );

And if you need to modify the name of the field (IBAN), you can do so with the wallets_fiat_ui_text_iban filter:

add_filter( 'wallets_fiat_ui_text_iban', function( $text ) {
	return 'Foo';
} );

Finally, if you need to modify the name of the option:

add_filter( 'wallets_ui_text_swiftbiciban', function( $text ) {
	return 'Other option';
} );

Please let me know if you have any questions.

with regards

[alexg]

Hello @pavelo65,

Sorry about the mixup, not sure why this happened. Your account should be ok now, please check again!

Please let me know if you encounter any more problems.

with regards

[alexg]

Hello,

No, there is nothing to apply as far as I know. Taproot should be transparent to the plugin.

Before release, I will test to ensure that the plugin will be compatible with the RPC API of the latest Bitcoin core, which at the time is 22.0.

It is possible that new deposit addresses will need to be created for all users – if so, I will include this in the release notes when the time comes.

with regards

[Author]

Posts