twelvebit

Swapsicle: CTO experience and website and dapp work

Website and decentralised application contributions recorded in the twelvebit portfolio, preserved here with visual references.

Our role: Former CTO (Rorrie); website and dapp development (twelvebit)

Swapsicle interface from the twelvebit portfolio
Portfolio record of Swapsicle. The project interface may have changed since this capture.

Project context

The twelvebit portfolio includes separate Swapsicle entries for a landing page and an exchange application. The website introduces the project, while the dapp interface provides the application context. Keeping those contributions separate helps explain the difference between a marketing surface and an interface used for blockchain interactions.

Our contribution

Rorrie Crocker, twelvebit’s director, previously served as CTO at Swapsicle. The twelvebit portfolio records website development for the landing page and dapp development for the exchange, alongside related Ice Cream Zombies website and dapp work. The former CTO role describes Rorrie’s experience; the portfolio entries describe the recorded development contributions. These do not establish ownership of the Swapsicle protocol or authorship of every part of its codebase.

Result and project reference

The retained screenshots show the landing-page and exchange interfaces associated with our work. The former public website and application targets were unavailable when checked on 12 October 2026, so this case study replaces those direct portfolio links. Swapsicle’s public GitHub organisation remains available as an additional project reference; it is not a substitute live exchange or proof that a specific repository matches the pictured release.

View the Swapsicle GitHub organisation

Historical portfolio work. Former website and exchange targets returned HTTP 402 on 12 October 2026.

Swapsicle landing-page portfolio capture
The landing page is a separate website-development contribution.

What this means for a similar project

A portfolio needs to remain useful when a client’s hosted service changes. Preserve a dated visual record and distinguish a historical contribution from a currently operated service. For a dapp engagement, the handover should also identify who owns hosting, network configuration and ongoing maintenance after delivery.

Explore our blockchain development service or discuss your project.

More portfolio work