fix(repo): remove fully

README.md

@@ -7,7 +7,7 @@
 </h1>
 
 <p align="center">
-  A fully decentralized, Ethereum-equivalent ZK-Rollup.
+  A decentralized, Ethereum-equivalent ZK-Rollup.
   <br />
   <a href="https://taiko.xyz" target="_blank"><strong>Explore the website</strong></a>
 </p>

packages/website/components/FeaturesSection.tsx

@@ -12,15 +12,15 @@ const features = [
     icon: ArrowPathIcon,
   },
   {
-    name: "Fully open source",
+    name: "Open source",
     description:
       "Taiko's code is open source and available on GitHub. Free to use and modify the source code with the permissive license.",
     icon: ScaleIcon,
   },
   {
-    name: "Fully decentralized",
+    name: "Decentralized",
     description:
-      "Fully decentralized and permissionless nodes, proposers, and provers. Anyone can participate in Taiko.",
+      "Decentralized and permissionless nodes, proposers, and provers. Anyone can participate in Taiko.",
     icon: GlobeAltIcon,
   },
 ];

packages/website/components/Hero.tsx

@@ -46,7 +46,7 @@ export default function Hero() {
                 A <span className="text-[#fc0fc0]">Type 1</span> ZK-EVM
               </h1>
               <p className="font-oxanium mt-3 text-lg text-neutral-600 sm:text-xl md:mt-5 dark:text-neutral-100">
-                Fully decentralized, Ethereum-equivalent ZK-Rollup.
+                Decentralized, Ethereum-equivalent ZK-Rollup.
               </p>
               <div className="mt-10 flex md:justify-left">
                 <div className="inline-flex rounded-md shadow">

packages/website/pages/docs/index.mdx

@@ -1,12 +1,12 @@
 ## Welcome to Taiko!
 
-Taiko is a fully decentralized, Ethereum-equivalent ZK-Rollup ([Type 1 ZK-EVM](https://mirror.xyz/labs.taiko.eth/w7NSKDeKfJoEy0p89I9feixKfdK-20JgWF9HZzxfeBo)). Taiko is working on the full Ethereum [ZK-EVM circuits](https://github.com/privacy-scaling-explorations/zkevm-circuits) as part of a community effort led by the EF's PSE team.
+Taiko is a decentralized, Ethereum-equivalent ZK-Rollup ([Type 1 ZK-EVM](https://mirror.xyz/labs.taiko.eth/w7NSKDeKfJoEy0p89I9feixKfdK-20JgWF9HZzxfeBo)). Taiko is working on the full Ethereum [ZK-EVM circuits](https://github.com/privacy-scaling-explorations/zkevm-circuits) as part of a community effort led by the EF's PSE team.
 
 Check the Taiko Roadmap [here](/images/roadmaps/taiko-roadmap.png).
 
 ## Contribute to Taiko
 
-Taiko is a fully open source and community driven project, check out the [contributing guide](https://github.com/taikoxyz/taiko-mono/blob/main/CONTRIBUTING.md) to get started as a contributor!
+Taiko is a open source and community driven project, check out the [contributing guide](https://github.com/taikoxyz/taiko-mono/blob/main/CONTRIBUTING.md) to get started as a contributor!
 
 ## Join the Discord
 

packages/website/pages/docs/resources/presentations.md

@@ -2,7 +2,7 @@
 
 - `2023-04-14`: [What's Taiko, Why Taiko?](https://www.youtube.com/watch?v=cbAYOsp8CTA&t=2717s) (ETHGlobal Tokyo)
 - `2023-04-14`: [Intro to Taiko: Using Ethereum-equivalence for ZK-EVM superpowers](https://www.youtube.com/watch?v=ud9Xy1woW2g&t=2615s) (ETHGlobal Tokyo Workshop)
-- `2023-04-08`: [Fully decentralized, Ethereum-equivalent ZK Rollup](https://hackmd.io/@taikolabs/H1gWNMAb3) (ETHGlobal Tokyo
+- `2023-04-08`: [Decentralized, Ethereum-equivalent ZK Rollup](https://hackmd.io/@taikolabs/H1gWNMAb3) (ETHGlobal Tokyo
 Builders Session)
 - `2023-03-14`: [Introduction to Taiko + Ethereum Dapp Speedrun with SvelteKit and Foundry](https://youtu.be/mgSBhreBQWA) (Scaling Ethereum — ETHGlobal)
 - `2023-03-01`: [Taiko ZK-EVM: Inheriting Layer 1 Security](https://hackmd.io/@taikolabs/BkWoN0nRi) (Security Day — ETHDenver)

packages/whitepaper/main.tex

@@ -122,13 +122,13 @@ \section{Design Principles}
 \item \textbf{Ethereum-Equivalent.} The design should stick to the design of Ethereum as closely as possible, not only for compatibility reasons but also for the expectations and demands of users of Ethereum L2 solutions.
 \end{enumerate}
 
-With these principles, our objective is to design and implement a fully Ethereum-equivalent (type-1) ZK-Rollup \cite{vitalik-zkevm}. This not only means that Taiko can directly interpret EVM bytecode, but also uses the same hash functions, state trees, transaction trees, precompiled contracts, and other in-consensus logic. We do however disable certain EIPs in the initial implementation\cite{taikoprotogithub} that will be re-enabled later (see Section \ref{sec:eips}).
+With these principles, our objective is to design and implement an Ethereum-equivalent (type-1) ZK-Rollup \cite{vitalik-zkevm}. This not only means that Taiko can directly interpret EVM bytecode, but also uses the same hash functions, state trees, transaction trees, precompiled contracts, and other in-consensus logic. We do however disable certain EIPs in the initial implementation\cite{taikoprotogithub} that will be re-enabled later (see Section \ref{sec:eips}).
 
 \section{Overview}\label{sec:properties}
 
 Taiko aims to build a secure, decentralized and permissionless rollup on Ethereum. These requirements dictate the following properties:
 \begin{enumerate}
-\item All block data required to reconstruct the post-block state needs to be put on Ethereum so it is publicly available. If this would not be the case, Taiko would not only fail to be a rollup but would also fail to be fully decentralized. This data is required so that anyone can know the latest chain state and so that useful new blocks can be appended to the chain. For the decentralization of the proof generation Taiko requires an even stronger requirement: all block data needed to be able to re-execute all work in a block in a step-by-step fashion needs to be made public. This makes it possible for provers to generate a proof for a block using only publicly known data.
+\item All block data required to reconstruct the post-block state needs to be put on Ethereum so it is publicly available. If this would not be the case, Taiko would not only fail to be a rollup but would also fail to be decentralized. This data is required so that anyone can know the latest chain state and so that useful new blocks can be appended to the chain. For the decentralization of the proof generation Taiko requires an even stronger requirement: all block data needed to be able to re-execute all work in a block in a step-by-step fashion needs to be made public. This makes it possible for provers to generate a proof for a block using only publicly known data.
 \item Creating and proposing blocks should be a fast and efficient process. Anyone should be able to add blocks to the chain on a level playing field, having access to the same chain data at all times. Proposers, of course, should be able to compete on e.g. transaction fees and \emph{Maximal Extractable Value} (MEV) \cite{mev}.
 \end{enumerate}