<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Searchers on Signet</title><link>https://test.signet.sh/docs/searchers/</link><description>Recent content in Searchers on Signet</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://test.signet.sh/docs/searchers/index.xml" rel="self" type="application/rss+xml"/><item><title>Fetching transactions</title><link>https://test.signet.sh/docs/searchers/fetching-transactions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://test.signet.sh/docs/searchers/fetching-transactions/</guid><description>&lt;aside class="callout callout--info"&gt;
 &lt;div class="callout-title"&gt;The Signet transaction cache&lt;/div&gt;
 Signet&amp;rsquo;s transaction cache stores pending transactions, orders and bundles submitted to the network, providing MEV searchers with a stream of opportunities without having to run their orderflow infrastructure. We&amp;rsquo;ll focus on the basics of fetching transactions.
&lt;/aside&gt;
&lt;p&gt;Transactions can be fetched from Signet&amp;rsquo;s transaction cache. Fetching transactions is easy with Signet&amp;rsquo;s Transaction Cache Client. Consult the &lt;a href="https://test.signet.sh/docs/build-on-signet/parmigiana/"&gt;Parmigiana Quickstart&lt;/a&gt; for any other RPC endpoints or contract addresses you might need.&lt;/p&gt;</description></item><item><title>Signed orders</title><link>https://test.signet.sh/docs/searchers/signed-orders/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://test.signet.sh/docs/searchers/signed-orders/</guid><description>&lt;h1 id="signed-orders"&gt;Signed Orders&lt;/h1&gt;&lt;aside class="callout callout--info"&gt;
 &lt;div class="callout-title"&gt;Signing Orders&lt;/div&gt;
 Signet&amp;rsquo;s Permit2 integration enhances token transfers by enabling intent-based orders with user signatures and Filler submissions.
&lt;/aside&gt;
&lt;h2 id="constructing-token-transfers"&gt;Constructing Token Transfers&lt;a href="#constructing-token-transfers" class="heading-anchor" data-heading-anchor aria-label="Link to Constructing Token Transfers"&gt;
 &lt;svg class="heading-anchor-icon" data-icon width="12" height="12" aria-hidden="true"&gt;
 &lt;use xlink:href="#icon-link"&gt;&lt;/use&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;&lt;strong&gt;Assemble Data&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Create the &lt;code&gt;outputs&lt;/code&gt; array specifying the tokens, amounts, recipients, and destination chain IDs. Construct the &lt;code&gt;permit&lt;/code&gt; object listing permitted tokens and amounts, along with the &lt;code&gt;nonce&lt;/code&gt; and &lt;code&gt;deadline&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Generate Witness Hash&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;Hash the &lt;code&gt;outputs&lt;/code&gt; array to create a witness hash, ensuring the integrity of the transaction details.&lt;/p&gt;</description></item><item><title>Filler</title><link>https://test.signet.sh/docs/searchers/filler/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://test.signet.sh/docs/searchers/filler/</guid><description>&lt;h1 id="filler"&gt;Filler&lt;/h1&gt;&lt;p&gt;The &lt;code&gt;Filler&lt;/code&gt; struct from &lt;a href="https://docs.rs/signet-orders/latest/signet_orders/" rel="noopener noreferrer" target="_blank"&gt;&lt;code&gt;signet-orders&lt;/code&gt;&lt;/a&gt;
orchestrates the full order-filling pipeline: fetching pending orders from a
source, signing &lt;a href="https://docs.uniswap.org/contracts/permit2/overview" rel="noopener noreferrer" target="_blank"&gt;Permit2&lt;/a&gt;
fills, and submitting them as bundles. It is the main building block for writing
a Signet filler bot.&lt;/p&gt;
&lt;aside class="callout callout--info"&gt;
 &lt;div class="callout-title"&gt;Example implementation&lt;/div&gt;
 The &lt;a href="https://github.com/init4tech/signet-filler" rel="noopener noreferrer" target="_blank"&gt;signet-filler&lt;/a&gt; repository is an
example filler built on top of &lt;code&gt;Filler&lt;/code&gt; and &lt;code&gt;FeePolicySubmitter&lt;/code&gt;. It demonstrates
order filtering, metrics, provider setup, and the overall structure of a filler
service.
&lt;/aside&gt;
&lt;h2 id="setup"&gt;Setup&lt;a href="#setup" class="heading-anchor" data-heading-anchor aria-label="Link to Setup"&gt;
 &lt;svg class="heading-anchor-icon" data-icon width="12" height="12" aria-hidden="true"&gt;
 &lt;use xlink:href="#icon-link"&gt;&lt;/use&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;div class="code-block" data-code-block&gt;
 &lt;div class="code-header"&gt;
 &lt;span class="code-lang"&gt;bash&lt;/span&gt;
 &lt;button class="code-copy" data-copy-button aria-label="Copy code" type="button"&gt;Copy&lt;/button&gt;
 &lt;/div&gt;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;cargo add signet-orders signet-types signet-constants signet-tx-cache
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;cargo add alloy --features provider-http,signers
&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;cargo add futures-util&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
&lt;h2 id="architecture"&gt;Architecture&lt;a href="#architecture" class="heading-anchor" data-heading-anchor aria-label="Link to Architecture"&gt;
 &lt;svg class="heading-anchor-icon" data-icon width="12" height="12" aria-hidden="true"&gt;
 &lt;use xlink:href="#icon-link"&gt;&lt;/use&gt;
 &lt;/svg&gt;
 &lt;/a&gt;
&lt;/h2&gt;&lt;p&gt;&lt;code&gt;Filler&lt;/code&gt; is generic over three type parameters:&lt;/p&gt;</description></item></channel></rss>