You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have recently created a new ERC20 TOKEN that works perfectly for buying and it is showing in the cryptocurrencies list. However, in order to implement the AML (Anti-Money Laundering) and Anti Smurf protocols, we need the TOKEN to be shown in the list of the Output Queues list of coins.
We understand that the Output Queues list is primarily used for transactions and we are requesting guidance on how to implement it for our new ERC20 TOKEN. We would greatly appreciate any assistance you can provide in order to ensure that our TOKEN is fully compliant with AML and Anti Smurf protocols.
Please let us know if any additional information is needed to assist with this request.
Thank you for your time and assistance.
Best regards,
Enrique Souza
The text was updated successfully, but these errors were encountered:
Hi Enrique,
this might be an issue with the Output Queues form.
Can you try to copy your version of currencies*.jar that you compile from this repository and that would contain your new coin and place it into /batm/app/master/lib/currencies-1.0.69.jar if that helps?
Dear General Bytes,
We have recently created a new ERC20 TOKEN that works perfectly for buying and it is showing in the cryptocurrencies list. However, in order to implement the AML (Anti-Money Laundering) and Anti Smurf protocols, we need the TOKEN to be shown in the list of the Output Queues list of coins.
We understand that the Output Queues list is primarily used for transactions and we are requesting guidance on how to implement it for our new ERC20 TOKEN. We would greatly appreciate any assistance you can provide in order to ensure that our TOKEN is fully compliant with AML and Anti Smurf protocols.
Please let us know if any additional information is needed to assist with this request.
Thank you for your time and assistance.
Best regards,
Enrique Souza
The text was updated successfully, but these errors were encountered: