搭建BSC Fullnode
要运行BSC全节点,首先需要有服务器,币安官方推荐服务器配置VPS running recent versions of Mac OS X or Linux.IMPORTANT 2T GB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 250MB/S throughput, read latency <1ms. (if start with snap/fast sync, it will need NVMe SSD)16 cores of CPU and 64 gigabytes of memory (RAM).Suggest m5zn.3xlarge instance type on AWS, c2-standard-16 on Google cloud.A broadband Internet connection with upload/download speeds of 5 megabyte per second我是在aliyun买的VPS,配置是16核64G,系统盘40G,数据盘3000G ESSD...
以Synthetix为例,MEV策略剖析
本文翻译自Robert Miller的Anatomy of an MEV Strategy: Synthetix 几个月前臭名昭著的alpha泄露者KALEB在Flashbots公开的searchers频道发表了下列消息KALBE泄露了关于Synthetix变动的数千万美金的alpha消息。在这个机器人运营商的小房间里分享alpha就像丢给狮子一块红肉一样,在快速看了合约之后可以确认有笔另人晕眩的钱处在危机中。 在接下来的几周,我计划并且尝试去执行策略来捕获KALEB分享的MEV。我会开源我用的代码并一步一步展示整个过程和策略。你将不能运行我的代码去赚钱,但是这篇文章将会教你我是如何设计这个新的搜索者并会包含许多alpha。很自然的,这将会有点技术性,但我会尽量让本文对于非技术读者来说好理解。第一步,识别机会我不是一个Synthetix专家,因此第一步是去学习我将要涉及的操作。具体如下:我找出了相关合约我在Synthetix博客里读了它们的高级别功能并且搜索了相关文档我确保理解了将要实行的治理变动我查找了相关函数总结一下这阶段的工作,Synthetix已经试验了以ETH为抵押去铸...
Bitmap结构在ENSToken里的应用
在ENSToken的合约里看到了Bitmaps的应用,在地址认领空投时用了Merkle树证明来check用户地址和认领数量,进而会对应一个Merkle的index,为了防止重复认领空投,合约里用了OpenZeppelin的Bitmaps库来做位图存储,地址认领成功后,就将对应的index在位图里存true,下次如果再来认领就会判断这个位图,如果为true时就返回错误,以此来防止重复认领空投。BitMaps.BitMap private claimed; /** * @dev Claims airdropped tokens. * @param amount The amount of the claim being made. * @param delegate The address the tokenholder wants to delegate their votes to. * @param merkleProof A merkle proof proving the claim is valid. */ function claimTokens(uint256 amo...
<100 subscribers
搭建BSC Fullnode
要运行BSC全节点,首先需要有服务器,币安官方推荐服务器配置VPS running recent versions of Mac OS X or Linux.IMPORTANT 2T GB of free disk space, solid-state drive(SSD), gp3, 8k IOPS, 250MB/S throughput, read latency <1ms. (if start with snap/fast sync, it will need NVMe SSD)16 cores of CPU and 64 gigabytes of memory (RAM).Suggest m5zn.3xlarge instance type on AWS, c2-standard-16 on Google cloud.A broadband Internet connection with upload/download speeds of 5 megabyte per second我是在aliyun买的VPS,配置是16核64G,系统盘40G,数据盘3000G ESSD...
以Synthetix为例,MEV策略剖析
本文翻译自Robert Miller的Anatomy of an MEV Strategy: Synthetix 几个月前臭名昭著的alpha泄露者KALEB在Flashbots公开的searchers频道发表了下列消息KALBE泄露了关于Synthetix变动的数千万美金的alpha消息。在这个机器人运营商的小房间里分享alpha就像丢给狮子一块红肉一样,在快速看了合约之后可以确认有笔另人晕眩的钱处在危机中。 在接下来的几周,我计划并且尝试去执行策略来捕获KALEB分享的MEV。我会开源我用的代码并一步一步展示整个过程和策略。你将不能运行我的代码去赚钱,但是这篇文章将会教你我是如何设计这个新的搜索者并会包含许多alpha。很自然的,这将会有点技术性,但我会尽量让本文对于非技术读者来说好理解。第一步,识别机会我不是一个Synthetix专家,因此第一步是去学习我将要涉及的操作。具体如下:我找出了相关合约我在Synthetix博客里读了它们的高级别功能并且搜索了相关文档我确保理解了将要实行的治理变动我查找了相关函数总结一下这阶段的工作,Synthetix已经试验了以ETH为抵押去铸...
Bitmap结构在ENSToken里的应用
在ENSToken的合约里看到了Bitmaps的应用,在地址认领空投时用了Merkle树证明来check用户地址和认领数量,进而会对应一个Merkle的index,为了防止重复认领空投,合约里用了OpenZeppelin的Bitmaps库来做位图存储,地址认领成功后,就将对应的index在位图里存true,下次如果再来认领就会判断这个位图,如果为true时就返回错误,以此来防止重复认领空投。BitMaps.BitMap private claimed; /** * @dev Claims airdropped tokens. * @param amount The amount of the claim being made. * @param delegate The address the tokenholder wants to delegate their votes to. * @param merkleProof A merkle proof proving the claim is valid. */ function claimTokens(uint256 amo...
Share Dialog
Share Dialog
多签钱包需要维护多个钱包所有者地址,满足一定数量的签名后,才可以发起交易。如果只用一个数组address[]去存储所有者地址,在检查某地址是否是所有者地址时需要遍历此数组,时间效率是O(n)。为了提高到O(1),通常做法可以是增加一个mapping(address=>bool)来存储某地址是否是所有者地址,但这样下来增加了storage的操作。Gnosis safe用了一个哨兵mapping来存储,可以改善此问题。
address internal constant SENTINEL_OWNERS = address(0x1);
mapping(address => address) internal owners;
假设有A,B,C三个所有者地址,储存到owners后,变为
owners[address(0x1)] = A
owners[A] = B
owners[B] = C
owners[C] = address(0x1)
这样,要判断某地址是否属于所有者地址时,只需O(1),且storage只用了一个mapping
function isOwner(address owner) public view returns (bool) {
return owner != SENTINEL_OWNERS && owners[owner] != address(0);
}
如果要增加一个D地址,则变为
owners[address(0x1)] = D
owners[D] = A
owners[A] = B
owners[B] = C
owners[C] = address(0x1)
时间效率也是O(1),相应代码是(此处只列出动态链表相关操作的代码)
function addOwner(address owner){
owners[owner] = owners[SENTINEL_OWNERS];
owners[SENTINEL_OWNERS] = owner;
}
如果要删除B地址,则变为
owners[address(0x1)] = D
owners[D] = A
owners[A] = C
owners[C] = address(0x1)
时间效率也是O(1),相应代码是(此处只列出动态链表相关操作的代码)
function removeOwner(address prevOwner,address owner){
owners[prevOwner] = owners[owner];
owners[owner] = address(0);
}//这里需要先在链下查到要删除地址的前一个地址,再直接传参数到链上去删除,节省链上计算gas
总体来说,这种数据结构还是很实用的,在gas cost上也很有帮助。
多签钱包需要维护多个钱包所有者地址,满足一定数量的签名后,才可以发起交易。如果只用一个数组address[]去存储所有者地址,在检查某地址是否是所有者地址时需要遍历此数组,时间效率是O(n)。为了提高到O(1),通常做法可以是增加一个mapping(address=>bool)来存储某地址是否是所有者地址,但这样下来增加了storage的操作。Gnosis safe用了一个哨兵mapping来存储,可以改善此问题。
address internal constant SENTINEL_OWNERS = address(0x1);
mapping(address => address) internal owners;
假设有A,B,C三个所有者地址,储存到owners后,变为
owners[address(0x1)] = A
owners[A] = B
owners[B] = C
owners[C] = address(0x1)
这样,要判断某地址是否属于所有者地址时,只需O(1),且storage只用了一个mapping
function isOwner(address owner) public view returns (bool) {
return owner != SENTINEL_OWNERS && owners[owner] != address(0);
}
如果要增加一个D地址,则变为
owners[address(0x1)] = D
owners[D] = A
owners[A] = B
owners[B] = C
owners[C] = address(0x1)
时间效率也是O(1),相应代码是(此处只列出动态链表相关操作的代码)
function addOwner(address owner){
owners[owner] = owners[SENTINEL_OWNERS];
owners[SENTINEL_OWNERS] = owner;
}
如果要删除B地址,则变为
owners[address(0x1)] = D
owners[D] = A
owners[A] = C
owners[C] = address(0x1)
时间效率也是O(1),相应代码是(此处只列出动态链表相关操作的代码)
function removeOwner(address prevOwner,address owner){
owners[prevOwner] = owners[owner];
owners[owner] = address(0);
}//这里需要先在链下查到要删除地址的前一个地址,再直接传参数到链上去删除,节省链上计算gas
总体来说,这种数据结构还是很实用的,在gas cost上也很有帮助。
No comments yet