Royco / Royco Protocol

Royco Protocol allows anyone to create a market around any onchain transaction (or series of transactions). Using Royco:

• Incentive Providers may create intents to offer incentives to users to perform the transaction(s).
• Users may create intents to complete the transaction(s) and/or negotiate for more incentives.

When these intents satisfy each other, the onchain transaction(s) execute atomically alongside the distribution of incentives. Royco Protocol is entirely non-custodial, trustless, and permissionless. It is also capital-efficient, allowing participants to create many intents with the same assets.

IAMs can be used to find efficient pricing for any onchain action, including depositing, staking, lending, voting, minting an NFT, etc.

Prize distribution and scoring

• Total Prize Pool: $30,000

• The prize distribution has 2 possible triggers:

  • If one or more valid medium severity findings are found, the total pot size is $7,500
  • If one or more valid high severity findings are found, the total pot size is $30,000

• Only High and Medium findings will be considered for the rewards

• Scoring described in the competition scoring page.

• Findings Severities described in detail on our docs page.

Documentation

• Technical Documentation

Scope

• Repository: roycoprotocol/royco

• Commit(latest): 2afa977dab20f7e5ab9b540e6c6381c5f635423f Please note: the above commithash is updated version. Cantina code uses a previous outdated commit 504c50b. Please use the latest version from github to download and use locally. The latest commit has the following changes: https://github.com/roycoprotocol/royco/commit/2afa977dab20f7e5ab9b540e6c6381c5f635423f

• nSLOC: 1050

Contracts

Smart contract	nSLOC
WeirollWallet.sol	74
RecipeOrderbook.sol	442
ERC4626i.sol	293
VaultOrderbook.sol	123
PointsFactory.sol	13
Points.sol	58
ERC4626iFactory	47

Build Instructions

• Compile and build:

  • Install foundry
  • forge compile,
  • forge install
  • forge build

• Basic POC test

  • And can be run with forge test –mt ScenarioTest

Out of scope

Known Issues:

• Royco allows permissionless vault/recipe creation so honeypots and malicious/broken vaults will need to be filtered out on the frontend

• Frontend Fee can be “stolen” by manually editing function parameters to pay the frontend fee someone other than the frontend

• Automated findings by Lightchaser

  • Royco-Protocol

Contact Us

For any issues or concerns regarding this competition, please reach out to the Cantina core team through the Cantina Discord.