Q: Blockchain / CLI / Secrets manager
So blockchain in this context admittedly sounds a bit gimmicky to me at face value.
But I would love to be informed on why this is not the case and in fact a brilliant choice for your product.
Do you have a CLI? Can it be used as a secrets manager for build pipelines?
What kinds of credentials do you support? Like how 1password has SSH keys, api key, databases etc. item types for example. It can generate SSH keys conveniently also.
Can we make our own item type templates?
Thanks!

MertBaser_TransferChain
May 21, 2025A: Hi Misty60110 👋🏻
Awesome questions, happy to dive into each one:
1️⃣
We don’t find your skepticism about “gimmicky” features surprising, because most people approach blockchain as a fake value proposition rather than something to truly benefit from. But with TransferChain, it’s the exact opposite. By its very nature, blockchain provides us with three fundamental advantages: decentralized and distributed data management, an immutable ledger, and auditability. These are benefits that traditional database management simply cannot offer.
When using TransferChain, it’s necessary to record certain key data about your transactions. If we were to do this using a traditional database —like every other solution on the market today— we would be storing information about your data in a system fully controlled and managed by us—where we could make retroactive changes, and even if we stored it encrypted or hashed, it would still create an attack surface for malicious actors - or in other words "a single point of failure". However, this would directly contradict our core principle: “Your data must always remain under your exclusive control.” That’s why storing this data on a blockchain network makes it immutable, secure, and consistently available—eliminating the risks associated with centralized control.
Furthermore, blockchain isn’t just used for system-level operations; it also manages the relationship and authorization between sender and receiver. In traditional solutions, these kinds of authorizations are handled in a database where the control is centralized. But blockchain, both by design and through components offers extremely high fault tolerance, the ability to become even more distributed over time, and the distribution of authority in a homogeneous manner. For example, in TransferChain Pass, every time you share a password with another user, both symmetric and asymmetric encryption are applied—and the entire authorization process is securely handled by the blockchain network.
As a result, no malicious actor can halt the process, manipulate data, or perform retroactive actions. Most importantly, blockchain ensures that the user can trust only themselves when it comes to their data and account integrity, security, and privacy—and that’s one of the fundamental reasons we use it.
In other words, on TransferChain Pass your passwords are not just secure — it’s Yours.
2️⃣
We currently have a CLI for TransferChain Drive, but not yet for Pass.
That said, the idea of using it as a secrets manager for building pipelines is spot-on — and it’s already sparked internal discussions with our team. We’ll be exploring it more seriously in our next team meeting.
3️⃣
Right now, username + password entries are fully supported — and you can technically store anything in the fields (some enterprise users told us that they use it for API keys or license info already) - but yes it’s not the most efficient way.
Therefore in June, we’re releasing a new item type: Secure Notes 📝
This will give you a cleaner structure for storing non-login credentials — API keys, tokens, config snippets, SSH keys, etc.
4️⃣
Not yet — we haven’t extended the UI to support that level of customization. Right now, we’re prioritizing the mobile apps and the secure notes.
Hope all of this is helpful, and we hope we can bring true security to your credentials as well!
— Mert | TransferChain 🔐