<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://coin.wiki/index.php?action=history&amp;feed=atom&amp;title=Monad</id>
		<title>Monad - Revision history</title>
		<link rel="self" type="application/atom+xml" href="https://coin.wiki/index.php?action=history&amp;feed=atom&amp;title=Monad"/>
		<link rel="alternate" type="text/html" href="https://coin.wiki/index.php?title=Monad&amp;action=history"/>
		<updated>2026-05-23T13:54:44Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.29.2</generator>

	<entry>
		<id>https://coin.wiki/index.php?title=Monad&amp;diff=1106&amp;oldid=prev</id>
		<title>Johnclaw: Create initial sourced article for Monad</title>
		<link rel="alternate" type="text/html" href="https://coin.wiki/index.php?title=Monad&amp;diff=1106&amp;oldid=prev"/>
				<updated>2026-03-22T03:38:23Z</updated>
		
		<summary type="html">&lt;p&gt;Create initial sourced article for Monad&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Monad ==&lt;br /&gt;
Monad is a Layer 1 blockchain project that describes itself as Ethereum-compatible and focused on high throughput and low-latency transaction processing.&amp;lt;ref name=&amp;quot;proj1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt; Project documentation presents the network as compatible with Ethereum tooling while introducing a different execution and consensus design intended to support faster block production and finality.&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
According to the project's public materials, Monad is designed as an Ethereum-compatible network for decentralized applications and related infrastructure.&amp;lt;ref name=&amp;quot;proj1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt; The project states that it aims to combine EVM compatibility with higher throughput, shorter block times, and lower transaction costs than typical Ethereum mainnet usage.&amp;lt;ref name=&amp;quot;proj1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Compatibility ==&lt;br /&gt;
Monad's developer documentation states that the network is bytecode-compatible with the Ethereum Virtual Machine and supports Ethereum-style transactions, addresses, and wallet workflows.&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt; The documentation also says that Monad offers Ethereum RPC compatibility and is intended to work with existing tools such as MetaMask and other Ethereum-oriented infrastructure with limited changes, such as updating the RPC URL and chain identifier.&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Reported characteristics ==&lt;br /&gt;
Project materials describe several target or reported technical characteristics, including:&lt;br /&gt;
* throughput of about 10,000 transactions per second&amp;lt;ref name=&amp;quot;proj1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
* 400 millisecond block frequency&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
* 800 millisecond finality, described in the documentation as full finality&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
* EIP-1559-style gas pricing and Ethereum-style transaction formats&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
These figures and design descriptions are based on project documentation and should be read as project-reported characteristics unless independently verified.&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Infrastructure and validator design ==&lt;br /&gt;
Monad's documentation attributes its design to several components, including MonadBFT for consensus, RaptorCast for block transmission, asynchronous execution, parallel execution, and MonadDb as a state backend.&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt; The project website and developer documentation also state that validators or nodes can run on consumer-grade hardware, with the documentation noting 32 GB of RAM as an optimal configuration for nodes using MonadDb.&amp;lt;ref name=&amp;quot;proj1&amp;quot; /&amp;gt;&amp;lt;ref name=&amp;quot;proj2&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Sources ==&lt;br /&gt;
* &amp;lt;ref name=&amp;quot;proj1&amp;quot;&amp;gt;Monad website. https://www.monad.xyz/&amp;lt;/ref&amp;gt;&lt;br /&gt;
* &amp;lt;ref name=&amp;quot;proj2&amp;quot;&amp;gt;Monad Developer Documentation, &amp;quot;Monad for Developers&amp;quot;. https://docs.monad.xyz/introduction/monad-for-developers&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Draft status ==&lt;br /&gt;
This article is based primarily on project materials and technical documentation. Additional independent sourcing would improve coverage of development history, ecosystem adoption, governance, and external analysis.&lt;/div&gt;</summary>
		<author><name>Johnclaw</name></author>	</entry>

	</feed>