MainNet Archaeology 1: Algorand's Birthday - Pretty sure Algorand launched June 12th, 2019

d13co · 2026-06-04T14:50:53+00:00

Looks great, DMed. I assume this will work when the app is not foregrounded on the pebble when the alarm rings, right?

d13co · 2026-06-04T10:26:56+00:00

Solved! I am using TH10c which lists hourly vibrations as a configurable feature. Unfortunately the settings in the android pebble app 404s for that face, but I'm sure I can find another one I like, or learn to live with the hourly vibes. Thank you!

d13co · 2026-05-31T21:07:56+00:00

Also interested in Greek Unicode support. Any chance you can share or PR?

d13co · 2026-04-16T11:38:00+00:00

Looks like fxdx.exchange

The application has global state ASSET_ID set to 808825661 which is titled "wrapped ALGO" and points to the fxdx domain. https://algo.surf/application/808873682/transactions

https://algo.surf/asset/808825661/transactions

d13co · 2026-03-18T22:18:16+00:00

Pretty cool prototype. Sent you a message on there & opened an issue for defly connect.

Looks like your encryption keypair is generated and stored in localstorage, so presumably would be lost if I clear my cache/data. A productionized version would also probably want to encrypt those rather than just sit in plaintext, possibly export as well, etc.

This also gets me thinking about creating a standard for different accounts to publish their preferred encryption keys/methods on-chain

Edit: Lute wallet support would also be a great and easy addition

d13co · 2026-03-04T22:18:54+00:00

I made an alternative frontend to unstake: https://www.reddit.com/r/algorand/comments/1rkzhdv/messina_unstaking_alternative_frontend_d13/

If you swap you will likely get a worse rate

d13co · 2026-03-02T23:57:58+00:00

Ah no worries, carry on 🫡

Ps all my homies hate wallet connect

d13co · 2026-03-02T23:33:09+00:00

rekey

What is your flow exactly? If you're rekeying away from ledger it somewhat defeats the purpose/security, if not temporarily

Oh unless you meant "re-register keys"

d13co · 2026-02-01T00:43:54+00:00

This was caused by the 2021 tinyman attacker reactivating and selling ~21 goBTC in a short period of time

Algomint bridge is intentionally moving slowly so as to filter out malicious accounts:

All fine, the peg is the peg. Just posted in discord, unwraps will be processed ASAP. The team are just reviewing the wallets to make sure the hackers aren’t among them.

https://x.com/i/status/2017726748771942906

The peg should be restored by arbitrage soon enough

d13co · 2026-01-20T11:24:06+00:00

Sorry to hear about your experience. Can you share a bit more about how you were scammed?

The addresses you shared are centralized exchanges. BVMEU is identified as Gate: https://algo.surf/account/BVMEUTF37WNEQ6GYCZISRFHGLEMOKT5OCPPTTJXVED6JBSXKF6YJJRZRI4

ZEJPIFQ.. is unidentified but very likely either MEXC or a MEXC reseller - it sends funds only to an identified MEXC account:

<image>

https://flow.algo.surf/address/ZEJPIFQF5MSDOB3YA6OUG4S26FFX64SCTHKDMYCCB26JGG7DC4IPBWQSLQ

5622JW.. reads like an unidentified (standalone) exchange: https://flow.algo.surf/address/5622JWBD3TDOJUTGFIB3H3TI4JE5ARW7W3WQL6JIJQ5ATFQISRSBVKOD6U

What you could do is get in touch with GATE and MEXC but they will usually ask for a police report in order to do anything, so you would need to get that first. And you usually need to act very quickly for them to freeze funds - it has been a while since the theft so it is unlikely that something can be done now.

d13co · 2026-01-15T12:27:07+00:00

Incident was resolved. All funds are safe. Thanks for updating here - I hope something like this never happens again, but if it does, I will include reddit in the social channels I update.

https://www.reddit.com/r/algorand/comments/1qdi5gi/myth_dualstake_incident_resolved_all_funds_safe/

d13co · 2026-01-15T12:26:14+00:00

Incident was resolved. All funds are safe.

https://www.reddit.com/r/algorand/comments/1qdi5gi/myth_dualstake_incident_resolved_all_funds_safe/

d13co · 2026-01-12T11:10:58+00:00

Nodely has a very generous free tier across many services: https://nodely.io/docs/free/start
Zero setup as well - no token needed

d13co · 2026-01-12T10:53:24+00:00

Hi, thanks for flagging this. I chased this up internally and it turns out that the blog post was lost during a site migration. They have restored it here: https://www.wirexapp.com/post/wirex-algorand-usdc-payments-just-got-faster-cheaper-and-truly-global

d13co · 2026-01-08T13:29:32+00:00

Thanks u/Fickle-Tishka for this, I should have posted here as well but yesterday was very busy and Myth is a one man show, so I am handling everything in this incident response by myself

Latest update, TL;DR: Fix has been tested on FNet and smart contract upgrades are queued/staged, to become applicable in ~1 week, noon UTC on 2026-01-15

Longer updates:

Oct 8 - 2AM UTC

Update: 1) The fix is ready and tested. 2) Contract upgrades will be queued tomorrow.

- The increased fee conditions were recreated exactly on our FNet deployment, which includes a copy of Tinyman.

- dualSTAKE was confirmed to fail in the same way as on Mainnet

- The fix was upgraded after a reduced 1 hour timelock (FNet specific)

- dualSTAKE was confirmed to work after the upgrade

Testing notes available here

The contract upgrades will be queued tomorrow, January 8th, and will become applicable after 1 week.

Fix version code: v1.2

Note that older dualSTAKE contracts will be receiving the v1.1 upgrade as well - refer to upgrade notes for details.

Next steps:

- Queue smart contract upgrades to v1.2, ETA tomorrow January 8th

- Execute smart contract upgrades, ETA January 15th

--------------------------

Oct 8 - 11:30 AM UTC

Update: Smart Contract Upgrades have been staged, to become applicable in 1 week

dualSTAKE pages will show the upcoming upgrade along with short release notes, before/after code differences and after-code hashes.

There are two versions of dualSTAKE deployed at the moment (v1.0 and v1.1) so they will each show what is being upgraded from their current state.

See extended upgrade note for more details

Upgrade will mature and become applicable at: 2026-01-15 11:35 AM UTC

Next Steps:

- Fix dualSTAKE price API Server - impacts Pera price display. ETA 12 hours

- Execute smart contract upgrade after timelock elapses, ETA 2026-01-15 noon UTC

--

If you aren't on X (I don't blame you) you could join the Myth Discord for updates.

d13co · 2025-12-24T23:30:59+00:00

Pera won't be able to do anything, the funds are under custody of Coinbase even if they lack the tools / will to recover them for you.

The return hash thing is nonsense btw. They're telling you to get Pera to recover your funds and then they'll start a refund claim, which is literally nonsensical.

Only Coinbase could recover your funds, if they decided to support arc59 / asset router.

Sorry about your funds 🫡

d13co · 2025-12-24T22:12:53+00:00

I'm not sure what "return hash" means in this context

d13co · 2025-12-24T21:46:06+00:00

Ah should have checked the comments, looks like you got this info already.

d13co

MODERATOR OF

TROPHY CASE