Software you write for interface = frontend Software you write for databases, apis, and other systems = backend Software you write for blockchains, smart contracts = ???
I can't think of a name 😆 the chain doesn't end and we sometimes work with Hyperstuctures so how bout 𝘏𝘠𝘗𝘌𝘙𝘗𝘖𝘚𝘐𝘛𝘐𝘖𝘕
Or does the backend just become “blockchain backend” or “onchain backend”?
I've always considered APIs as another form of frontend. Leaving the backend mostly to data, background tasks, etc. Blockchains are the backend and Smart Contracts are a mix since they define storage and business logic but also APIs which I consider frontend.
Chain code, consensus code, application code, contract code In interchain world we’re calling it app layer code, or ( :/ ) dApp code Although iOS autocorrected dapp to dApp so maybe that’s a legit thing now
I usually use a `/contracts` dir But `/contracts` excludes other blockchain related software, like subgraphs or dune sql queries Blockchain is primarily responsible for tracking global states, so maybe: project /frontend /backend /state /contracts /subgraph /dune
A separation is also needed for blockchains as contracts/app layer are very different from nodes/protocol
I'd still stick in the backend realm. Blockchain = AWS, Smart Contract = backend application layer
