Version control the spec. Not just the code.
If the spec is the source of truth, your app can be built from scratch, rebuilt or refactored. By AI that knows exactly what you intended.
This is the spec-driven development Kiro @kirodotdev trying to bring. You start with intent, not code. Record what features does, why it was built that way, the architecture decisions behind it. All living under the specs folder. Only then AI start building.
It reminded me of something my senior used to drill into me. "Don't just write what you did in the pull request and commit message, write why you did it."
Ethereum Attestation Service (EAS) runs on 2 smart contracts:
SchemaRegistry: register the shape of data
EAS: sign and store attestations
That's the entire protocol.
Just infrastructure.
Ethereum Attestation Service (EAS) @eas_eth lets any address digitally sign structured data on-chain, or off-chain.
Off-chain attestations are completely free, an EIP-712 signature, nothing touches the blockchain.
On-chain attestations cost gas, but on layer2 like Base it's fractions of a cent.
Trust, made programmable.
Ethereum Attestation Service (EAS) @eas_eth lets any address digitally sign structured data on-chain, or off-chain.
Off-chain attestations are completely free, an EIP-712 signature, nothing touches the blockchain.
On-chain attestations cost gas, but on layer2 like Base it's fractions of a cent.
Trust, made programmable.