Decentralized ownership of architectural designs: is blockchain the solution?
One of the recurring challenges in architecture and design is ownership and attribution of work. With so many stakeholders — architects, engineers, contractors, and clients — it can be difficult to prove who created what, and when.
I’ve been exploring how blockchain might address this problem. By recording designs, revisions, or even 3D model versions on a decentralized ledger, you could create a transparent and tamper-proof history of ownership. This could help protect intellectual property, resolve disputes, and even open new ways of licensing or sharing architectural designs in open-source communities.
Some firms are already experimenting with this concept. For example, Pixel Web Solutions, a custom blockchain development company, has been working on blockchain applications outside of finance, including use cases where design ownership and authenticity need to be verified. Their work shows how these ideas could be adapted to industries like architecture.
I’m curious what the OSArch community thinks — could decentralized ownership actually work for architectural designs, or is it too complex to integrate with current workflows?
Comments
We have distributed proof of authorship with code-signing in Git - without the massive computational overhead of a blockchain.
Bonsai doesn't have a gui option for signing (though it could be added if there is demand), but you can automatically sign all commits to a repository with
git config commit.gpgsign true(configure your keys first).However this will only provide provenance, for ownership and distribution rights we really ought to have a standardised License Pset.
The "blockchain" is a solution without a problem. Well, except for gambling.
I think it would be cool to explore using the blockchain and concepts like DAO's to equitably distribute architecture/engineering fees among a group of collaborators on a project.
That way, individual scopes don't have to be so delineated to begin with. It would afford more agility and crossover where one team member can fill the gaps of the other, and vice versa.
At periodic points in the project the team could log, on the blockchain, their vote on how fees should be distributed. Votes could be periodic weighted to safeguard against gaming, etc.