Notification Suggestion

[Anonymous]

Hi Alex,

I’ve added a explorer link the withdrawal transaction notification:

Transaction Link: https://chainz.cryptoid.info/###SYMBOL###/tx.dws?###TXID###

But cryptoid doesn’t support the symbol to be in CAPS. Would it be possible to add another variable for the symbol in small letters? like ###SYMBOLsmall###?

Regards Philipp

[alexg]

Hello Philipp,

Block explorer links do not accept variables in the same way that email templates do.

your link would be something like https://chainz.cryptoid.info/XYZ/tx.dws?%s

Where XYZ would be your coin and %s is substituted with the TXID using the PHP sprintf function.

I can make it so that %2$s is lowercase TXID while %s or %1$s is the current uppercase value.

This will go into the next release.

regards

[Anonymous]

Well the txid works fine. Just cryptoid can’t handle XYZ as symbol they need xyz.

[alexg]

OK in that case you should enter the coin symbol in lowercase.

There is no variable for the coin. Enter one link pattern per coin.

[Anonymous]

I just need the ###SYMBOL### (XYZ) and ###SYMBOLsmall### (xyz). Would that be possible?

[alexg]

Hello,

No, actually variable substitution is not needed in the block explorer links.

You can enter the coin symbol in lowercase as part of the URI.

There are instructions on how to do this in the manual.

kind regards

[Anonymous]

For me it is. My service supports multiple coins but I only have one notification. So I need a variable to determine the coin.

[alexg]

OK sounds like you could be doing something wrong.

There are three places where you can enter a blockexplorer url:

1. When you extend the Dashed_Slug_Coin_Adapter class to create your own coin adapter from scratch, you can override the methods explorer_uri_transaction() and explorer_uri_address(). You can use the method get_symbol() to constuct your URI based on the actual symbol of the instance. You could define an abstract subclass that returns something like 'https://chainz.cryptoid.info/' . $this->get_symbol() . '/tx.dws?%s' and then not have to worry about this in any concrete implementations for each coin you instantiate.

2. You can provide a URI by binding to the filter: wallets_explorer_uri_tx_XXX or the filter: wallets_explorer_uri_add_XXX where XXX is a coin symbol. In this case you have no choice – you have to use the XXX symbol in your URI pattern since it is already part of the filter you are binding to.

3. In the MultiAdapter’s coins.csv file. Again, in this file every line is its own coin, so again you have to use the coin symbol as part of the URI.

Hope this is clearer. I do not want to change the URI pattern, because that would break things. I am confused by what you mentioned “My service supports multiple coins but I only have one notification” Block explorer URIs have nothing to do with the notification mechanism. If you insist that none of the above solutions work for you, could you please explain why in more detail?

Thank you very much

kind regards
Alex

[Author]

Posts