[alexg]

Hello,

Keeping you updated on this issue:

We now know that the above issues you mentioned were possible when using MyISAM as a MySQL table storage engine. The plugin since warns the user about converting the tables to InnoDB.

Moreover, with the recent feature of available balance calculations, these balance-related issues are now resolved.

with regards

[alexg]

I have not tested quark.

What’s important is not the mining algorithm, but whether the JSON-RPC API is the same as Bitcoin. If it is, then it will work with the Full Node Multi Coin adapter.

The commands that are used by the plugin are: getinfo or getwalletinfo, getnewaddress, sendtoaddress, gettransaction, getblock, listtransactions. If these work the same as in Bitcoin, you’re good to go.

with regards

[alexg]

Hello,

Thanks for reporting.

There are some minor issues with the deposit shortcode, I have now fixed these and the fix will be in the next release.

In general, it is not a good idea to put all of the shortcodes in one page. Some shortcodes work only with cryptocurrencies, others with fiat currencies, and some work with both. So they try to keep in sync where possible, but this can be confusing to end users, therefore I believe it’s best to break the presentation of the shortcodes into multiple pages.

with regards

[alexg]

Hello,

The instructions are the ones I just gave you here. There is nothing else to it.

Other material that you can also review: https://www.dashed-slug.net/developers-coin-adapters-api/

There is also some info in the documentation under the “Adapters” section.

Follow the instructions and ask me if you get stuck.

Also, you do not need to edit any files. I would recommend that you create your own adapter class, and add it into a plugin file in any way you see fit. Just remember to make the code include/require the class file on the wallets_declare_adapters action, as discussed above.

with regards

[alexg]

Glad to hear that the issue was resolved.

If you see the warning about wp_cron persisting, then you can set up manual cron triggering (ask me how to do this if you are not sure how). If on the other hand you only saw the error once, you can ignore it.

If you have already set up manual cron triggering and you still see this error, this means that the cron job runs but does not complete. I would need to see the verbose debug output to determine where the job fails.

with regards

[alexg]

Hello Megan,

You are correct, this would be useful, I hadn’t thought of it. I will make a note and try to implement it in one of the future releases of the coin adapter extension.

with regards

[alexg]

https://purdyalerts.com

[alexg]

Hello again,

I have a solution:

function wallets_rates_rapidcoin( $rates ) {
	$data = json_decode( file_get_contents( 'https://api.coingecko.com/api/v3/simple/price?ids=rapids&vs_currencies=USD,BTC' ) );

	if ( $data ) {
		$rates['USD_RPD'] = $data->rapids->usd;
		$rates['BTC_RPD'] = $data->rapids->btc;
	}
	return $rates;
}

add_filter( 'wallets_rates', 'wallets_rates_rapidcoin', 100 );

You can insert this into your theme or as a separate one-file plugin.

Or, if you are using a file similar to this one, you can add the code at the bottom of the file.

with regards

[alexg]

I have made a bad assumption, that coin symbols are unique, when in fact they are not.

The price you see is not that of RapidCoin (RPD) but that of Ripped (RPD).

Let me think about how to approach this…

[alexg]

Thank you. That’s great news!

Don’t forget to disable Verbose log output (debug) otherwise your logfiles will fill up quickly.

with regards

[alexg]

Ignore my last question, you already mentioned which providers you are using.

[alexg]

Hello Megan,

Thank you as always for the detailed screenshots.

My first thought would be that there is maybe a fiat currency from fixer, with the same symbol, overwriting the value. This is not the case.

Which Exchange rate providers are you using? Do you have only CoinGecko enabled?

I will investigate and let you know.

It shouldn’t be necessary, but if you want to force a reload of all exchange rates, it is very easy if you are using wp-cli:

wp option delete wallets_rates
wp transient delete wallets_rates_last_run

I will investigate on my end and let you know shortly what I found.

with regards

[alexg]

Hello,

The high-level architecture is as follows:

The parent plugin is responsible for holding a list of transactions for each user account. From this the balance is calculated on the fly.

The coin adapters are responsible for communicating with wallets. They do the withdrawals and notify the plugin of incoming deposits.

The Exchange extension holds markets, orderbooks, orders and trades. It affects the balances by inserting trade transactions in the transaction table of the parent plugin.

What you want to do, would be possible with a coin adapter. If you are interested in a simple example of how this works, you can have a look at the now deprecated Litecoin adapter. The Full Node Multi Coin Adapter is the evolution of that, for handling multiple wallets.

If you attempt to develop your own coin adapter, feel free to ask me any questions. You should start by subclassing Dashed_Slug_Wallets_Coin_Adapter. Implement the abstract methods and override the other methods as needed. Then, make sure the class still has a no-argument constructor, and include the class file on the wallets_declare_adapters action. The plugin will discover and instantiate your adapter using reflection.

with regards

[alexg]

Helo Megan, that’s great news! I will release a patch for the exchange extension with only this fix for now.

with regards

[alexg]

Hello,

Yes, it could, but it is probably best to interface to an existing, well-established referral plugin. I have not yet began analysis on this task so I don’t know which way is best yet.

with regards

[Author]

Posts