Thread by @StillAgyle

Dear @wearetalisman users,

I want to address the current status of Talisman’s efforts to go open-source as I’ve dun goofed a number of times and over-represented how fast this would happen in various tweets and comments.

A Thread 🧵

#polkadot

First let me say we are absolutely going to open-source Talisman!

This means every repo and every line of code will be made public and licensed under Apache 2.0, our repos have been audited a number of times and we are ready to open up the codebase.

So when will it happen?

The answer is I’m not sure, but ASAP.

Currently we’re blocked only by small legal issues.

These relate to corporate restructuring we started 2022 to better manage long-term systemic risks.

In hindsight I’d like us to have gone open source from the start.

So why didn’t we?

They say that imitation is the sincerest form of flattery.

Well, on a number of occasions in the early days of Talisman we found ourselves overwhelmingly flattered by our competitors in the market, so we opted to close the codebase.

But the community can still trust us, right?

Despite having a seasoned team, multiple audits, and using best practices, the incompetence of the wider market cast doubt on Talisman too.

There’s no better example than Slope wallet, who published user secrets to 3rd party monitoring tools, causing over 9k wallet exploits. 🤦‍♂️

The time has come for the prodigal son of @Polkadot to return home and pay their penance.

If it’s not verifiable, it’s not web3. Let’s build a future with less trust and more truth.

Soon friends, Talisman will be open source.