Intuition is an Ethereum-based attestation protocol harnessing the wisdom of the crowds to create an open knowledge and reputation graph. Our infrastructure makes it easy for applications and their users to capture, explore, and curate verifiable data. We’ve prioritized making developer integrations easy and have implemented incentive structures that prioritize ‘useful’ data and discourage spam.
In bringing this new data layer to the decentralized web, we’re opening the flood gates to countless new use cases that we believe will kick off a consumer application boom.
The Intuition Knowledge Graph will be recognized as an organic flywheel, where the more developers that implement it, the more valuable the data it houses becomes.
To get a basic understanding of the Intuition protocol, please check out the following:
- Share prices may get arbitrarily large as deposits/withdraws occur after Vault asset and share amounts approach 0 (i.e. if all users have withdrawn from the Vault), but this still elegantly achieves our desired functionality - which is, Users earn fee revenue when they are shareholders of a vault and deposit/redeem activities occur while they remain shareholders. This novel share price mechanism is used in lieu of a side-pocket reward pool for gas efficiency.
- The Admin can pause the contracts, though there is an emergency withdraw that allows users to withdraw from the contract even while paused. This emergency withdraw bypasses all fees, to reduce the surface area of attack.
- Exit fees are configurable, but have a maximum limit which they can be set to, preventing loss of user funds. Users also have the timelock window to withdraw from the contracts if they do not agree with a parameter change.
To build the project and run tests, follow these steps:
$ npm i
$ forge install$ forge build$ forge test -vvv- Make sure you have at least node 16 and python 3.6 installed on your local machine
- Add your FUZZ_AP_KEY to the .env file locally
- Run the following command to install the
diligence-fuzzingpackage:
$ pip3 install diligence-fuzzing- After the installation is completed, run the fuzzing CLI:
$ fuzz forge test-
Finally, check your Diligence Fuzzing dashboard to see the results of the fuzzing tests
-
On newer versions of Python, you may receive this error:
ModuleNotFoundError: No module named 'distutils'In this case, you just need to install setuptools because distutils was deprecated in Python 3.10:
$ pip3 install setuptools- Install the
slither-analyzerpackage:
$ pip3 install slither-analyzer- After the installation is completed, run the slither analysis bash script:
$ npm run slither-
Make sure you have Docker installed on your local machine
-
Build the Docker image:
$ docker build -t manticore-analysis .- Run the Docker container:
$ docker run --rm -v "$(pwd)":/app manticore-analysisTo deploy the Beta smart contract system on to a public testnet or mainnet, you’ll need the following:
- RPC URL of the network that you’re trying to deploy to (as for us, we’re targeting Base Sepolia testnet as our target chain for the testnet deployments)
- Export
PRIVATE_KEYof a deployer account in the terminal, and fund it with some test ETH to be able to cover the gas fees for the smart contract deployments - For Base Sepolia, there is a reliable testnet faucet deployed by Alchemy
- Deploy smart contracts using the following command:
$ forge script script/Deploy.s.sol --broadcast --rpc-url <your_rpc_url> --private-key $PRIVATE_KEYTo verify the deployed smart contracts on Etherscan, you’ll need to export your Etherscan API key as ETHERSCAN_API_KEY in the terminal, and then run the following command:
$ forge verify-contract <0x_contract_address> ContractName --watch --chain-id <chain_id>Notes:
- When verifying your smart contracts, you can use an optional parameter
--constructor-argsto pass the constructor arguments of the smart contract in the ABI-encoded format - The chain ID for Base Sepolia is
84532, whereas the chain ID for Base Mainnet is8453
To upgrade the smart contract you need:
- Deploy a new version of contracts you want to upgrade, for example
MultiVault. You need to add the directive@custom:oz-upgrades-fromon the line before where you define the contract and set the version of the upgrade on theinitfunction (e.g.reinitializer(2)) - If using a multisig as an upgrade admin, schedule the upgrade for some time in the future (e.g. 2 days) using this script to generate the parameters that can be used in Safe Transaction Builder:
$ forge script script/TimelockController.s.sol- After the delay passes (e.g. 2 days) you can call this again, just change the method on the target to
execute
Bonding curves have been added for the Atom / Triple vaults. When creating an Atom or a Triple, you must specify a Bonding Curve ID.
- If you are in doubt of which curve to use, select ID '1' for the Linear curve.
- Additional bonding curves will be added over time. Currently we have the Linear curve, the Logarithmic curve and the Stepped Logarithmic Curve
- A bonding curve is set upon creating the Atom / Triple and cannot be changed after.
- New bonding curves are registered with the BondingCurveRegistry contract, after they are deployed.
- All bonding curves implement the BaseCurve abstract contract.
- Different bonding curves create varying incentive mechanisms for users to stake.
Here is a visualization of the Logarithmic Bonding Curve, initialized with a scale of 2e18, an offset of 1, and a divisor of 1e18: [] 1.0 ether -> 0.802469135802469132 e18 shares [] 2.0 ether -> 1.333333333333333332 e18 shares [] 3.0 ether -> 1.704 e18 shares [] 4.0 ether -> 1.975308641975308636 e18 shares [] 5.0 ether -> 2.181729834791059276 e18 shares [______] 6.0 ether -> 2.34375 e18 shares [] 7.0 ether -> 2.474165523548239592 e18 shares [] 8.0 ether -> 2.581333333333333332 e18 shares [] 9.0 ether -> 2.670924117205108934 e18 shares [] 10.0 ether -> 2.746913580246913576 e18 shares [] 11.0 ether -> 2.812168108026096186 e18 shares [] 12.0 ether -> 2.868804664723032064 e18 shares [] 13.0 ether -> 2.918419753086419746 e18 shares [] 14.0 ether -> 2.962239583333333332 e18 shares [] 15.0 ether -> 3.001221249745572966 e18 shares [_] 16.0 ether -> 3.036122542295381794 e18 shares [] 17.0 ether -> 3.067551149341497782 e18 shares [] 18.0 ether -> 3.096 e18 shares [] 19.0 ether -> 3.12187308785948241 e18 shares [] 20.0 ether -> 3.145504633107938886 e18 shares [] 21.0 ether -> 3.167173502095832986 e18 shares [] 22.0 ether -> 3.187114197530864192 e18 shares [] 23.0 ether -> 3.205525333333333332 e18 shares [] 24.0 ether -> 3.22257624032771961 e18 shares
The bars show the ratio of the assets staked to the total shares returned. The Scale can be changed to adjust this.
New curves can be visualized using testVisualizeLogarithmicCurve in the BondingCurveRegistry.t.sol test.
The Stepped Logarithmic Curve is still in development, but in it's current state is useful for scaling the logarithmic values by the desired ratio.
ProxyAdmin: TBD
TimelockController (proxy admin owner): TBD
MultiVault (proxy address): TBD
Admin Safe: 0xa28d4AAcA48bE54824dA53a19b05121DE71Ef480
Trust: 0x6cd905dF2Ed214b22e0d48FF17CD4200C1C6d8A3
TrustBonding: TBD
TrustUnlockFactory: TBD
ProxyAdmin: TBD
TimelockController (proxy admin owner): TBD
MultiVault (proxy address): TBD
Admin Safe: 0xEcAc3Da134C2e5f492B702546c8aaeD2793965BB
Trust: TBD
TrustBonding: TBD
TrustUnlockFactory: TBD