Igor Artamonov

Unfortunately, I don't think we have any resources available to support any additional chains including BSC. We consider providing this on a commercial basis, thought, if there is any interest....

Well, I mean we have to maintain the code specifics for the BSC if it's added and accept/fix bugs related to BSC, forever. That's a big commitment. Also run nodes...

It should be `options` attribute, like ``. You can check the sources here: https://github.com/emeraldpay/hashicon/blob/master/packages/hashicon-react/src/component.tsx

Thank you for your input. We were using it as a standalone server mostly, i.e. always expected all of the features. Though now we started to use it as a...

@thomaseizinger thank you! going to heavily refactor it for the next version, and will fix that as well

It seems that the original data (which I see as a `raw_data` field) has a field called `id` which is a UUID. It has different values for those transactions, and...

`unique_id` is a transaction hash for those withdrawals. But both withdrawals are in the same Bitcoin transactions, therefore it's the same string value.

Here is the error details from the log: ``` rp2.rp2_error.RP2RuntimeError: Internal error: transaction1.to_exchange and transaction2.to_exchange are both unknown: IntraTransaction: plugin=Coinbase unique_id=10515c4a87a1abd5036a8ab946ac21f96a756f7ddb2446f194757782058f331a raw_data={"id": "d3edbfd0-0478-4946-ae46-8bb7aeaa15b9", "type": "send", "status": "completed", "amount": {"amount": "-0.10000123",...

Right, it's two parts of the same transaction. Both are standard withdrawals to two different on-chain non-coinbase addresses. Just made with a single on-chain transaction, that's why they share the...

You don't need to do anything special. Just make a withdrawals via a standard Coinbase UI, then make another one in a minute or less. Most likely it will be...