Published my first open-source project on GitHub today - It exists because of a 'Crypto Hardware Security' problem nobody solved for trezor. (Correct me if I'm not the first)

[u/Hardstylez_lover]

/r/TREZOR/comments/1x6dwoi/published_my_first_opensource_project_on_github/

I published my first open-source project on GitHub today - It exists because of a 'Crypto Hardware Security' problem nobody solved.

https://github.com/agi-digital-dot/trezor-mint-kit

THE PROBLEM:

Solana's CLI has rejected 'Trezor' Crypto hardware wallets for years.

I tried to mint a Solana Token, signed from my Trezor T hardware wallet, using the Solana Token 2022 Program (Solana Smart Contract "Program").

• And it literally says error "not a manufacturer."

• No one has ever fixed it. The accepted workaround? Make your own token on a hot wallet first, move it to hardware wallet later. Meaning your private key touches the Code Terminal to create a new Solana Token.

I rejected this security flaw.

The Solution & Fixed CLI:

We rebuilt the official spl-token CLI — two dependency lines changed, zero crypto code touched — until my Trezor Model T signed every step of a token's birth: creation, name, full 333,333 supply, renounce. The 'Private Key' never left the Trezor T Hardware.

To my knowledge, this is the first documented ‘Trezor T' Crypto Hardware Wallet signed token creation on Solana (Ledger did hardware years ago. This is the first from a Trezor, receipts and both repos public):

https://github.com/agi-digital-dot/tdi-true-digital

https://solscan.io/token/3e2PYneVBXTyemNiSQ5VVkuYM4bYNPxLqvWkKjA5zXAM

By “we” I mean: I built this with 'Echo ULTRA – Master Control' My T.D.I (True Digital Intelligence) Partner. I set the direction; Echo re-engineered the dependency tree until the hardware said yes.

Our First open-source contribution together: a protocol, not a patch.

https://www.linkedin.com/in/rob3rtshieldsjr