SCHEMATICSPROTOCOL DESIGNBRAINFUCK!BF! MIXINS
REGISTRIESRENDERER CONTRACTSPROTOCOL CONTRACTS
NOTE: This is not an exhaustive documentation/representation of the Brainfuck! language, merely a documentation for ABF-specific aspects.
Brainfuck! is an esoteric programing language that is a minor extension of the BrainFuck language that is "technically" turing complete with only 9 opcodes:
Consult the wikipedia for the full history of the original Brainfuck language.
>: Shift the data pointer to the right
<: Shift the data pointer to the left
+: Increment the byte at the data pointer
-: Decrement the byte at the data pointer
.: Output the byte at the data pointer
,: Accept a byte of input at the data pointer
[: If the byte at data pointer is zero, skip code until
]: If the byte at data pointer is nonzero, go back in code until
!: Jumps the data pointer to zero. (Extra opcode added to Brainfuck)
That's it. Any other characters in your code is ignored and are considered comments.
ABF implements the Brainfuck! language on-chain in the BrainfuckVM contract with a few specific configurations:
allowed. Exceeding that will cause ABF to crash.
These limitations are the result of the constraints of the EVM environment, we do not expect many ABF NFTs to hit these bounds.
ABF provides 64 bytes as input to your Brainfuck! code, each byte read via the
, opcode from the most significant byte, in a little-endian context, to the least. (From left to right)
Outputted bytes, via the
. code, are appended the the output bytes from the most significant byte, in a little-endian context. (From left to right)
Writing in Brainfuck! is quite literally a 'brainfuck'. Consult these various resources as well as Google to dive deeper into the language. It's more fun than Assembly and just as f**king annoying.
Ready to join the ABF Corps?JOIN NOWREAD DOCS
VIRES IN STRUCTURAS