Idris Karam

Idris Karam covers blockchain infrastructure for TokenPR: consensus design, scaling architecture, smart contract security and the long unglamorous work of protocol upgrades.

They write from a build background rather than a finance one, having spent several years as a backend engineer before moving into technical writing and then reporting. It shows in the coverage. Idris reads the specification, the client release notes and, where it matters, the diff — and is willing to say when a launch described as a breakthrough is a parameter change.

Their recurring theme is that most of the interesting risk in this industry is not economic but operational. Bridges do not usually fail because the cryptography was wrong; they fail because a multisig had five signers and two of them shared a laptop. Upgradeable contracts do not fail because upgradeability is bad; they fail because nobody documented who holds the admin key. Idris covers those seams, and covers post-mortems seriously — including the ones teams would rather quietly delete.

They are careful with the word "decentralised". A network with ten thousand nodes and three entities producing every block is a specific arrangement with specific failure modes, and Idris prefers to describe the arrangement rather than argue about the label. Readers occasionally find this pedantic. Teams whose sequencer went down for six hours generally do not.

For the Crypto Marketing side of the site, Idris acts as the technical reviewer on any playbook that makes a claim about how something works, on the principle that a marketing guide which misdescribes the technology damages the client it was written to help.

They cover Blockchain Tech, Layer 1 and 2, Smart Contracts and Tech Updates, and hold the position that no protocol should be written about purely on the basis of its own documentation.