Profile of Eugene in Rari Foundation
Posts by Eugene
-
[RRC-XX] Enhancing Multichain Governance: Upgrading RARI DAO Token on Arbitrum and RARI chains
by Eugene - This user is a moderator
Posted on: Aug. 21, 2024, 12:36 p.m.
Content: Tokens were deployed on Arbitrum One and RARI chains:
https://arbiscan.io/address/ 0 xcf 78572 a 8 fe 97 b 2 b 9 a 4 b 9709 f 6 a 7 d 9 a 863 c 1 b 8 e 0 1
rari.calderaexplorer.xyz
Rari Mainnet address details for 0 xCf 78572 A 8 fE 97 b 2 B 9 a 4 B 9709 f 6 a 7 D 9 a 863 c 1 b 8 E 0 |... 2
View the account balance, transactions, and other data for 0 xCf 78572 A 8 fE 97 b 2 B 9 a 4 B 9709 f 6 a 7 D 9 a 863 c 1 b 8 E 0 on the Rari Mainnet (Rari Mainnet) Explorer
Bridges were not yet configured.
To configure Arbitrum Bridge an Arbitrum DAO proposal should be created
RARI chain bridge is WIP. ETA to complete - end of this week.
Let’s improve the governance, make it more accessible and easy-to-use
Likes: 4
Replies: 0
No replies yet.
-
[RRC-XX] Enhancing Multichain Governance: Upgrading RARI DAO Token on Arbitrum and RARI chains
by Eugene - This user is a moderator
Posted on: July 16, 2024, 6:14 a.m.
Content: Audit is here
Rari Bridged Token Security Analysis ( 2 ).pdf ( 237 . 1 KB)
Likes: 1
Replies: 0
No replies yet.
-
[RRC-XX] Enhancing Multichain Governance: Upgrading RARI DAO Token on Arbitrum and RARI chains
by Eugene - This user is a moderator
Posted on: July 16, 2024, 6:12 a.m.
Content: This is a draft proposal by the Rari Foundation to gather community feedback in order to finalize this proposal for submission to the Arbitrum DAO
Abstract
DAO seeks to enhance its governance framework by upgrading the RARI token contract and bringing governance from Ethereum mainnet to the Arbitrum ecosystem. This proposal outlines the implementation of a custom L 2 token on Arbitrum, facilitating efficient governance processes while reducing user costs and improving overall accessibility for the DAO. To register the custom L 2 token to custom gateway on Arbitrum native bridge there should be a voting on Arbitrum DAO. This proposal asks for the community feedback to finalize proposal to the Arbitrum DAO
Motivation
RARI DAO is governed by the $RARI token, which when locked in veRARI grants voting access. The current token contract is on Ethereum mainnet and is not upgradable. The RARI DAO wishes to upgrade its governance, a part of which is token contract upgrade with snapshots and delegations embedded but we lack the ability to change the mapping on the bridge router and custom gateway on the Arbitrum native bridge.
Rationale
The RARI DAO multichain governance upgrade is designed to make governance more accessible, by simplifying the UX, reducing gas fees, and enabling new token functions. This aligns with Artbitrum’s commitment to user-centricity and technical inclusivity.
With a custom L 2 token implementation we will be able to perform the RARI DAO governance upgrade and move our governance fully into the Arbitrum ecosystem.
Key terms
RARI token: RARI DAO governance token (https://etherscan.io/token/ 0 xfca 59 cd 816 ab 1 ead 66534 d 82 bc 21 e 7515 ce 441 cf
RARI DAO: body governing the Rarible Protocol and RARI chain
Custom L 2 RARI token: upgraded and simplified RARI token to be used in RARI DAO multichain governance moving forward
Smart Contract in question is in this PR: Implement bridged RARI token for Arbitrum ecosystem (Arbitrum + RARI chains) by evgenynacu · Pull Request # 305 · rarible/protocol-contracts · GitHub 1
Specifications
RARI token in question (https://etherscan.io/token/ 0 xfca 59 cd 816 ab 1 ead 66534 d 82 bc 21 e 7515 ce 441 cf) does not have upgradability nor allows the owner to register in the arbitrum token bridge router.
As such, we’re requesting a custom L 2 token implementation, and use the (standard) custom gateway. Lacking the ability to upgrade / owner-register, we are seeking Artbirum DAO’s approval to register the upgraded RARI token to the custom gateway so we can proceed with the custom L 2 implementation.
The upgraded token contract was fully audited and can be found here 1
Steps to implement
Deploy token contracts to Arbitrum and RARI chains. See implementation here 1 :
Change mapping for L 1 → L 2 tokens on bridge router and custom gateway (via Arbitrum DAO proposal)
Futher steps
New token contract is designed to be upgradeable. As soon as multichain governance is set up, permissions to upgrade token contract and to do other admin actions will be transferred to the DAO
Overall costs
N/A
Likes: 5
Replies: 0
No replies yet.
-
RRC-XX Implementing a RARI Protocol Fee
by Eugene - This user is a moderator
Posted on: July 16, 2024, 2:04 a.m.
Content: So, in total there should be 2 calls:
upgrade the contract
set protocol fees
Likes: 1
Replies: 0
No replies yet.
-
RRC-XX Implementing a RARI Protocol Fee
by Eugene - This user is a moderator
Posted on: July 16, 2024, 2:03 a.m.
Content: Here is the call to change protocol fee and receiver.
The call sets protocol fee to 0 . 25 % for each side
address: 0 xb 23 BCD 4 F 668365 B 1 c 9 Ec 4 B 4 DF 79915 bF 8 c 76 C 5 b 5
function: execute
params:
upgrade: 0 xcaC 1 fE 02 cB 051672 D 93 eE 390136 B 8 E 10301 B 6709
upgradeCallData: 0 x 828 bd 7 fe 0000000000000000000000007 e 9 c 956 e 3 efa 81 ace 71905 ff 0 daef 1 a 71 f 42 cbc 500000000000000000000000000000000000000000000000000000000000000190000000000000000000000000000000000000000000000000000000000000019
Here are encoded:
fee recipient ( 0 x 7 e 9 c 956 e 3 EFA 81 Ace 71905 Ff 0 dAEf 1 A 71 f 42 CBC 5 ),
protocol fee values ( 25 and 25 )
You can check executable code here:
https://etherscan.io/address/ 0 xcaC 1 fE 02 cB 051672 D 93 eE 390136 B 8 E 10301 B 6709 #code
Tenderly tx simulation is here:
dashboard.tenderly.co
Tenderly Dashboard
Tenderly is a full-stack infrastructure that gives Web 3 teams the only multichain node RPC with built-in development environments and debugging tools. Move fast from development to on-chain deployment across any EVM-compatible chain with a fully...
Likes: 2
Replies: 1
Replies:
- Eugene: So, in total there should be 2 calls:
upgrade the contract
set protocol fees
-
RRC-XX Implementing a RARI Protocol Fee
by Eugene - This user is a moderator
Posted on: June 27, 2024, 9:52 a.m.
Content: Protocol Exchange contract code is ready to be enabled on Ethereum mainnet - I just deployed it here:
0 x 1 F 90567 f 5 f 63 eAB 82 a 2 c 37414471 b 13 e 4896331 b
To prepare transaction for the proposal we need to come up with these parameters:
What will be seller and buyer protocol fee? Ideally it should be equal (as some application which use Exchange contract may not be ready for different values)
Address of the Treasury which will gather protocol fees
After that I can prepare transactions for enabling fee.
Meanwhile this is the calldata and params for upgrading the contract code:
address: 0 xb 23 BCD 4 F 668365 B 1 c 9 Ec 4 B 4 DF 79915 bF 8 c 76 C 5 b 5
function: execute
params:
upgrade: 0 xd 22 CD 47808 ae 4 b 13 D 46 Fa 8 FEFc 08 C 91 eb 5790 Bf 8 (this is ProxyUpgradeAction which only purpose is to upgrade contracts)
upgradeCallData: 0 xe 17 f 52 e 900000000000000000000000080033 c 932904 e 077 e 55 a 6 e 43 e 5 e 9 a 796 f 34 d 25250000000000000000000000009757 f 2 d 2 b 135150 bbeb 65308 d 4 a 91804107 cd 8 d 60000000000000000000000001 f 90567 f 5 f 63 eab 82 a 2 c 37414471 b 13 e 4896331 b (Here are encoded: proxy admin address, target upgradeable contract address and new implementation address: 0 x 80033 c 932904 E 077 e 55 a 6 E 43 E 5 E 9 a 796 f 34 d 2525 , 0 x 9757 F 2 d 2 b 135150 BBeb 65308 D 4 a 91804107 cd 8 D 6 , 0 x 1 F 90567 f 5 f 63 eAB 82 a 2 c 37414471 b 13 e 4896331 b)
Likes: 1
Replies: 2
Replies:
- addie: Here’s the tenderly simulation for this transaction:
dashboard.tenderly.co
Tenderly Dashboard
Tenderly is a full-stack infrastructure that gives Web3 teams the only multichain node RPC with built-in development environments and debugging tools. Move fast from development to on-chain deployment across any EVM-compatible chain with a fully...
- Eugene: Here is the call to change protocol fee and receiver.
The call sets protocol fee to 0.25% for each side
address: 0xb23BCD4F668365B1c9Ec4B4DF79915bF8c76C5b5
function: execute
params:
upgrade: 0xcaC1fE02cB051672D93eE390136B8E10301B6709
upgradeCallData: 0x828bd7fe0000000000000000000000007e9c956e3efa81ace71905ff0daef1a71f42cbc500000000000000000000000000000000000000000000000000000000000000190000000000000000000000000000000000000000000000000000000000000019
Here are encoded:
fee recipient (0x7e9c956e3EFA81Ace71905Ff0dAEf1A71f42CBC5),
protocol fee values (25 and 25)
You can check executable code here:
https://etherscan.io/address/0xcaC1fE02cB051672D93eE390136B8E10301B6709#code
Tenderly tx simulation is here:
dashboard.tenderly.co
Tenderly Dashboard
Tenderly is a full-stack infrastructure that gives Web3 teams the only multichain node RPC with built-in development environments and debugging tools. Move fast from development to on-chain deployment across any EVM-compatible chain with a fully...
-
RRC-XX Implementing a RARI Protocol Fee
by Eugene - This user is a moderator
Posted on: June 20, 2024, 1:07 p.m.
Content: Update: Protocol fees are almost ready to be launched.
Several PRs already merged and released. 2 PRs left: for Exchange contract and SDK
Both PRs have a goal: introduce new order version (V 3 ) which will pay protocol fees.
This is needed for backward compatibility for applications using the protocol.
Once the smart contract PR is accepted, contract code implementation can be deployed on-chain and proposal can be created on-chain
Likes: 4
Replies: 0
No replies yet.
-
RRC-XX Implementing a RARI Protocol Fee
by Eugene - This user is a moderator
Posted on: June 6, 2024, 8:38 a.m.
Content: @Matt_StableLab currently in Exchange contract there are 2 types of protocol fees: seller fee (will be taken from the seller) and buyer fee (buyer will pay more then).
These fees can be controlled separately, there are 2 fields which we can control.
So need to figure out how to configure 2 fees: should every part be 0 . 25 % then?
More information is here: protocol-contracts/projects/transfer-manager/contracts/RaribleTransferManager.md at master · rarible/protocol-contracts · GitHub 1
Likes: 3
Replies: 1
Replies:
- bitblondy: Are there examples from other chains regarding protocol fees? Would be interested in their experiences. And is it just for NFT trades, or for transactions in general?
I do think 0.5% is manageable, and would rather support a flat fee, to stay simple. The Tally feature to directly implement the fees on-chain sounds cool.
Would the generated fees benefit the DAO treasury in general? Maybe the fee would be better accepted if there was a specific cause determined, e.g. the generated fees will be used to support builders on the chain or incentives for users.
-
Security Council configured royalties for Yuga collections
by Eugene - This user is a moderator
Posted on: May 8, 2024, 10:58 a.m.
Content: Yuga reached to us and asked to update royalties for list of their smart-contracts. Operation could not be done by them because those contracts do not follow Ownable pattern.
Tx was initiated on Monday, 6 th of May 2024
All royalties were set in one tx: https://etherscan.io/tx/ 0 x 5766 a 6 d 5 e 8 c 286483 e 309 d 4 f 007 cfadbb 7 acdab 71802 b 6 a 89 d 3 a 48 d 98 d 008073 #eventlog 1
Likes: 5
Replies: 0
No replies yet.
-
RRC-14: Continuation of Rarible Protocol Transfer to Community
by Eugene - This user is a moderator
Posted on: Feb. 8, 2024, 11:10 a.m.
Content: We successfully transferred ownership of the protocol contracts to DAO.
Now we want to test if everything’s working ok.
For this we need to create a proposal which will do some action on the governed contracts.
I suggest to do some action which actually does nothing: sets protocol fee to zero.
Here’s the link: Placebo proposal to test if DAO voting process works with Protocol Contracts 10
Likes: 5
Replies: 0
No replies yet.
