Rook
Search…
Welcome
🔰
For Beginners
What is MEV?
What is a Keeper?
➿
Rook Protocol
Understand the Protocol
Hiding Book
Auctions
Reputation
Greenlight Algorithm
ROOK and xROOK
🤖
Integration guides
Integrate your Dapp/Wallet
Run a Market Maker
Run a Keeper
Keeper Pilot Program
Keeper Architecture
Keeper Addresses
Keeper Integration Guide
Block.timestamp vs order.expiry
HidingBook HTTP API
HidingBook WS API
Coordinator HTTP API
Coordinator WS API
Payment channels
🔖
Quick reference
Smart Contracts Registry
Contact Us
Blog
Discord
Powered By GitBook
Keeper Addresses
Keepers have 3 different types of addresses.

KeeperIdentityAddress (KIA)

  • This address represents the Keeper's identity. All other addresses are registered to this address.
  • Must be an EOA, so signatures can be created using this address's private key.
  • A Keeper must only have one of these. Keepers generate this address themselves. Contact Rook and inform them of your identity address to get started.
  • This address should not change over time.

KeeperStakeAddress (KSA)

  • This address calls the deposit() function to stake the ROOK on the staking contract.
  • Must be an EOA, so signatures can be created using this address's private key.
  • A Keeper may have many of these; however, most Keepers will only have one of these. We recommend using only one per trading operation. So if a Keeper is running multiple trading operations they can separate out the accounting for each by using separate stake addresses.
  • A Keeper registers this to a single KIA. Keepers generate this address themselves and inform Rook via registration API call to the HTTP server
  • This can be the same as your KIA

KeeperTakerAddress (KTA)

  • This address actually calls the trade function on-chain.
  • Can be a smart contract or an EOA.
  • A Keeper may have many of these. We recommend using as many of these as you prefer. Some Keepers may use a couple, others may use dozens. Using multiple KTAs makes your trading operation queue simultaneous trades more easily since you don't need to queue future nonces. Example: KTA1 for trade1 and KTA2 for trade2, as opposed to KTA1-nonce-1 for trade1 and KTA1-nonce-2 for trade 2.
  • A Keeper registers this to a single KIA. Keepers generate this address themselves and inform Rook via registration API call to the HTTP server
  • We do NOT recommend making this the same as your KIA because Keepers typically use many of these addresses and these may change over time, whereas your KIA should not change over time.
Previous
Keeper Architecture
Next
Keeper Integration Guide
Last modified 3mo ago
Copy link
Outline