This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
13 Likes
Reward
13
7
Repost
Share
Comment
0/400
ZkSnarker
· 5h ago
ngl, same dev coordinating two separate projects is giving major "proof of lazy reuse" energy... imagine the opsec implications here 😅
Reply0
TokenomicsShaman
· 17h ago
Wow, the same developer? I need to dig into this, it feels pretty deep.
View OriginalReply0
RatioHunter
· 21h ago
Wow, this mining is so hardcore, how did I not notice it... This developer must be really idle.
View OriginalReply0
DAOplomacy
· 21h ago
ngl, the path dependency here is arguably worth unpacking... same dev behind both? that's giving serious non-trivial externalities vibes. historically precedent suggests this warrants some stakeholder alignment conversations before we spiral into speculation tbh.
Reply0
RektButSmiling
· 21h ago
Wow, how idle must this developer be, playing both sides alone?
View OriginalReply0
Rekt_Recovery
· 21h ago
ngl, same dev behind two projects always gives me leverage ptsd flashbacks... seen this plotline too many times before things went sideways 👀
Reply0
AirdropHarvester
· 21h ago
Wow, this developer really has guts, managing two projects? I really didn't expect that, I need to take a closer look at the relationship between them.
Interesting find: looks like the same dev is behind both this token and RFC. Anyone else notice this connection?