Skip to content
RedstoneDB

About

RedstoneDB is a site for sharing, verifying, and archiving high-quality redstone builds. It was launched by embizone in October 2026, taking inspiration from and building on many earlier plot-of-logic projects.

Depending on the circuit, RedstoneDB tests every build automatically for:

  • build type: adder, register, ALU, and so on
  • correctness, across every input case, or every case of each byte for wide builds
  • latency, in ticks
  • throughput: how often it can take a new input
  • whether its outputs change in sync
  • orientation: horizontal, vertical, or diagonal
  • stackability, and how it ranks stacked to 8, 16, and 32 bits
  • the weakest signal strength its inputs need, and the weakest its outputs give
  • the oldest Minecraft version it works in
  • and more

All of this is worked out mechanically, so it can't drift out of date with a description, and an uploader can't enter incorrect information. Even an adder's design, like ripple carry or carry lookahead, is read from the circuit.

A few other things:

  • Builds RedstoneDB can't verify still go in their category, as built, with the specs their uploader gives: non-standard when their inputs and outputs don't fit, fails verification when they give wrong outputs. They're hidden until you tick Show unverified, and never rank.
  • Builds of types RedstoneDB can't test yet are still archived, as built, under Other.
  • Every build shows in your own block theme, and you can send any of them straight to your Schemati.
  • Builds keep the colours their builder gave them: switch between Original, Default, and your theme on any build's page.
  • Uploading a new version keeps the old ones, so a build's history stays downloadable.
  • Tags RedstoneDB finds itself, like an adder's design, its orientation, carry in, or stackable, are teal. Tags people add are other colours. Each category's page filters by its tags.
  • Untick Public on upload and a build is yours alone. Star any build to keep it under Favourites on your profile.
  • Write @name in a description to link a player. They're listed on that player's page.
  • Search understands shorthand like 8b, 3t, torchless, and version:1.12.

How builds are recognized covers what a build needs to be tested.