🧵 La Bobinerie - Haberdashery of Bobine modules: serious primitives, educational gems, and esoteric oddities. Grab, deploy, fork at will.

⸟

Available now:

• counter

  Per-account counter with Ed25519 session authentication.

• pool-xyk

  XYK (constant-product) AMM pool for two fungible tokens: add/remove liquidity, swap, fee in bps.

• say-my-name

  A simple name storage contract that remembers who you are.

• sigil

  Account-bound on-chain sigil (SVG PFP): mint one per derived address, optional on-chain tag.

• token_fungible

  A minimal fungible token module for Bobine, designed to be a boring, reliable building block for DeFi modules (pools, routers, etc.).

bobinerie/
├── contracts/               # All the smart contracts
│   └── say-my-name/         # A single contract
│       ├── contract.feature # BDD tests (specifications)
│       ├── out/             # Compiled outputs (WASM + types)
│       ├── README.md        # Contract documentation
│       ├── src
│       │   ├── mod.ts
│       │   └── mods
│       │       └── mod.ts
│       └── tsconfig.json
├── run/                     # Deployment & execution scripts
└── package.json             # Build scripts

npm install

Configure your Bobine server in .env.local (optional):

SERVER=http://localhost:8080

Compile all contracts:

npm run prepack

Deploy a contract:

CONTRACT=say-my-name npm run contract:produce
# Returns: { address: "3ca2c27f..." }

Other common tasks:

• Build a single contract: CONTRACT=say-my-name npm run contract:build
• Produce all contracts: npm run produce
• Generate docs: npm run docs
• Run tests: npm run test
• Run tests with coverage: npm run test:coverage (measures test infrastructure, not WASM contract code)

Execute a contract method:

npm run execute 3ca2c27f... sayMyName text:"Alice"

Got a useful contract? An intriguing experiment? Put it on the shelves.

1. Create your contract in contracts/your-contract-name/
2. Write comprehensive cucumber BDD tests in contracts/your-contract-name/contract.feature
3. Add JSDoc documentation to all public API functions
4. Run npm run docs to generate the READMEs
5. Submit a PR

All contributions welcome, from serious primitives to silly meme contracts.