We have conducted an investigation of the DB Alert situation, and determined that the Arkham alerts were sent accurately in this case.
DB set two alerts on all Bitcoin transactions above $10k USD, with no counterparties set, then named the alerts “Mt Gox” and “US Gov”.
When we fixed a bug causing us to not send alerts on configs like this, he then correctly received many alerts based on his parameters. No one received inaccurate alerts, they simply began receiving the alerts they had previously set.
Neither the alert nor the tweet could have caused the sharp BTC price drop today, as the drop occurred between 19:17 and 20:01 UTC, and the alerts and tweet were sent afterwards at 20:07 UTC and 20:08 UTC respectively.
4
@KeystoneWallet@phantom@solana Thanks for the reply. My largest concern would be avalanche support. I’d like to buy a few and then refer this to everyone in my community of 400 members. Our project uses avalanche and our only option right now is @Ledger It would be nice to have another option with a nice UI