關於 vector magic ，我們在網路上蒐集到這些相關的討論、資訊與評價

[143801] 10601. 噬魂者：靈魂共嗚～Soul、成為 死神之鐮？～"Soul Eater" Resonance of the Soul: Will Soul Eater Become a Death Scythe? (2008)★★★
[143802] 10602. 噬魂者：我才是明星！～最強的男人出現了？～"Soul Eater" I Am the Star!: The Big Man Is Showing Up Here? (2008)★★
[143803] 10603. 噬魂者：完美的少年～Death The Kid 的華麗任務？～"Soul Eater" The Perfect Boy: Death the Kid's Magnificent Mission? (2008)★★
[143804] 10604. 噬魂者：捕獵魔女發動！～心跳緊張♥墓地的補習授課？～"Soul Eater" Engage the Witch Hunter! A Remedial Lesson in the Graveyard? (2008)★★
[143805] 10605. 噬魂者：靈魂的形態～最強職人斯坦登場？～"Soul Eater" Shape of the Soul - Enter the Ultimate Meister Stein? (2008)★★
[143806] 10606. 噬魂者：傳說中的新生！～充滿回憶、Kid的死武專初次登校？～"Soul Eater" The New Student: Kid's First Day at the Academy - Will it be an Entrance to Remember? (2008)★★
[143807] 10607. 噬魂者：黑血的恐怖～可樂那的體內有武器？～"Soul Eater" Black-blooded Terror - There's a Weapon Inside Crona? (2008)★★
[143808] 10608. 噬魂者：魔女梅杜莎～擁有極其凶殘靈魂之人？～"Soul Eater" Medusa the Witch - The One Who Possesses a Great Evil Soul? (2008)★★
[143809] 10609. 噬魂者：聖劍傳說～Kid與Black Star的大冒險？～"Soul Eater" Legend of the Holy Sword - Kid and Black?Star's Great Adventure? (2008)★★
[143810] 10610. 噬魂者：妖刀正宗～突破靈魂附體、在雨中詠唱的心？～"Soul Eater" The Enchanted Sword Masamune - Break the Soul Possession: A Heart Sings in the Rain? (2008)★★

[143811] 10611. 噬魂者：椿之花～超越悲傷盡頭得到的是？～"Soul Eater" Tsubaki the Camellia Blossom - What Lies Beyond the Grief? (2008)★★
[143812] 10612. 噬魂者：不輸給恐懼的勇氣～瑪嘉．亞爾邦的第一大決心？～"Soul Eater" Courage That Beats Out Fear - Maka Albarn's Great Resolution? (2008)★★
[143813] 10613. 噬魂者：魔眼之男～Soul與瑪嘉、逐漸偏移的靈魂波長？～"Soul Eater" The Man with the Magic Eye - Soul and Maka's Diverging Soul Wavelength? (2008)★★
[143814] 10614. 噬魂者：超級筆記試驗～緊張緊張興奮興奮不安不安 不是吧？～"Soul Eater" The Super Written Exam - Heart-pounding, Reeling, and Restless. You're Kidding!? (2008)★★
[143815] 10615. 噬魂者：Soul的黑龍～膽小的莉絲與愉快的朋友們？～"Soul Eater" The Soul Eating Black Dragon - Scaredy-cat Liz and Her Merry Friends? (2008)★★
[143816] 10616. 噬魂者：激鬥！幽靈船～我腦中的地獄？～"Soul Eater" Fierce Battle Aboard the Ghost Ship - The Hell Inside My Head? (2008)★★
[143817] 10617. 噬魂者：聖劍傳說2～喝、打、買、事先聲明？～"Soul Eater" Legend of the Holy Sword 2 - Wanna Go Drinking, Gambling, and Playing? (2008)★★‒
[143818] 10618. 噬魂者：前夜祭的惡夢～並且開幕了？～"Soul Eater" The Eve Party Nightmare - And So the Curtain Rises? (2008)★★
[143819] 10619. 噬魂者：開始、地下攻防戰～突破吧、美杜莎的矢量箭？～"Soul Eater" The Underground Battle Commences - Break Through Medusa's Vector Arrow? (2008)★★
[143820] 10620. 噬魂者：黑血的共鳴戰！～迎戰恐怖的弱小靈魂的大奮鬥？～"Soul Eater" The Black Blood Resonance Battle! A Small Soul's Grand Struggle Against Fear? (2008)★★

[143821] 10621. 噬魂者：將我的靈魂〜送入乾涸的心、在無法忍受的孤獨中…？〜"Soul Eater" May My Soul Reach You - A Dry Heart Inside Unbearable Isolation? (2008)★★★
[143822] 10622. 噬魂者：封印之社〜不死男布下的陷阱？〜"Soul Eater" The Seal Shrine - The Immortal Man's Tricks? (2008)★★
[143823] 10623. 噬魂者：死亡與生存〜在復活與幻覺之間？〜"Soul Eater" Dead or Alive - In the Rift between Revival and Dazzlement? (2008)★★
[143824] 10624. 噬魂者：神之間的戰鬥〜Death City面臨毀壞的危機？〜"Soul Eater" The Battle of the Gods - Death City on the Verge of Collapse? (2008)★★
[143825] 10625. 噬魂者：死神之鐮集合〜爸爸的人事異動〜"Soul Eater" The Death Scythes Convene - Stop Dad's Staff Reassignment!? (2008)★★
[143826] 10626. 噬魂者：高興又害羞的入學體驗！～死武專新生活後援會召開中～"Soul Eater" The Exciting and Embarrassing Trial Enrollment! The DWMA New Lifestyle Support Fair is Open? (2008)★★
[143827] 10627. 噬魂者：800年的殺意！～異端魔女降臨～"Soul Eater" 800 Years of Bloodlust - Advent of the Heretic Witch? (2008)★★
[143828] 10628. 噬魂者：劍神屹立～味道是甜還是鹹～"Soul Eater" The Sword God Rises - Does it Have a Sweet or Salty Taste? (2008)★★
[143829] 10629. 噬魂者：美杜莎復活！～蜘蛛與蛇的再會～"Soul Eater" Medusa's Revival! A Spider and Snake's Fateful Reunion? (2008)★★
[143830] 10630. 噬魂者：炙熱的暴走！〜大魔導師遺留下來的魔道具？〜"Soul Eater" The Red Hot Runaway Express - A Magic Tool Left Behind by the Great Wizard? (2008)★★

[143831] 10631. 噬魂者：乾枯的幸福～在月光下閃耀的是誰的淚水？～"Soul Eater" Drying Happiness! Whose Tears Sparkle in the Moonlight? (2008)★★
[143832] 10632. 噬魂者：聖劍傳說3～死武專番長物語？～"Soul Eater" Legend of the Holy Sword 3 - The Academy Gang Leader's Tale? (2008)★★
[143833] 10633. 噬魂者：共鳴連鎖～奏起靈魂們的旋律？～"Soul Eater" Resonance Link - Play the Melody of the Souls? (2008)★★
[143834] 10634. 噬魂者：波亂爭奪戰！～激突、死武專VS蜘蛛恐怖？～"Soul Eater" The Battle for Brew - Clash: the DWMA vs. Arachnophobia? (2008)★★
[143835] 10635. 噬魂者：暴風摩斯基德～曾經的世界，限定時間是十分鐘？～"Soul Eater" Mosquito's Storm! Ten Minutes to Fight in the World of the Past? (2008)★★
[143836] 10636. 噬魂者：綻放，七人的共鳴連鎖～破壞與創造的演奏會？～"Soul Eater" Unleash the Seven's Resonance Link! A Recital of Destruction and Creation? (2008)★★
[143837] 10637. 噬魂者：名偵探的第一個事件～Kid發掘的死武專秘密？～"Soul Eater" The Detective's First Case - Kid Exposes the DWMA's Secret? (2008)★★
[143838] 10638. 噬魂者：通往修羅道的誘惑～偉大的男人無法抑制的焦慮？～"Soul Eater" Asura's Temptation - The Big Man's Uncontrollable Irritation? (2008)★★
[143839] 10639. 噬魂者：古落那，逃亡～請讓我看看，你的微笑？～"Soul Eater" Crona's Escape - Show Me Your Smile, Please? (2009)★★
[143840] 10640. 噬魂者：被切掉的牌～美杜莎，向死武專投降？～"Soul Eater" The Cards are Cut - Medusa Surrenders to the DWMA? (2009)★★

[143841] 10641. 噬魂者：旋轉不停～令博士起舞的新世界？～"Soul Eater" Twirl 'Round and 'Round - A New World in Which the Doc Dances? (2009)★★
[143842] 10642. 噬魂者：進攻！帕帕‧耶加之城～總覺得含糊不清？～"Soul Eater" Charge Baba Yaga's Castle! Things are Kind of Gloomy? (2009)★★
[143843] 10643. 噬魂者：最後的魔道具～赤手空拳的Kid之不可能的任務？～"Soul Eater" The Last Magic Tool - Mission Impossible for Unarmed Kid? (2009)★★
[143844] 10644. 噬魂者：膽小鬼可樂那的決心～獻給一直在身邊的你？～"Soul Eater" Weakling Crona's Determination - For You, for Always Being by My Side? (2009)★★
[143845] 10645. 噬魂者：退魔波長～猛攻，憤怒的魔人狩獵？～"Soul Eater" Anti-Magic Wavelength - Fierce Attack, the Anger-Filled Genie Hunter? (2009)★★
[143846] 10646. 噬魂者：武道還是修羅道～決戰，米夫內VS黑暗☆之星？～"Soul Eater" Warrior or Slaughterer? Showdown: Mifune vs. Black_Star? (2009)★★
[143847] 10647. 噬魂者：奇蹟的老爸翻桌～飛吧！我們的死亡之城機器人？～"Soul Eater" The Miraculous Coffee Table Flip - Fly, Our Death City Robot? (2009)★★
[143848] 10648. 噬魂者：手持死神之鐮的死神大人～事態突變，凶吉未卜？～"Soul Eater" Lord Death Wields a Death Scythe - Just One Step from Utter Darkness? (2009)★★
[143849] 10649. 噬魂者：阿修羅覺醒～世界終結的盡頭？～"Soul Eater" Asura Wakes - To the End of the World? (2009)★★
[143850] 10650. 噬魂者：聽天由命？！～超越神的男人們？～／暗號就是勇氣！"Soul Eater" Sink or Swim?! The Men who Transcend the Gods? / The Word is Bravery! (2009)★★

📜 [專欄新文章] Reason Why You Should Use EIP1167 Proxy Contract. (With Tutorial)
✍️ Ping Chen
📥 歡迎投稿： https://medium.com/taipei-ethereum-meetup #徵技術分享文 #使用心得 #教學文 #medium

EIP1167 minimal proxy contract is a standardized, gas-efficient way to deploy a bunch of contract clones from a factory.

1. Who may consider using EIP1167

For some DApp that are creating clones of a contract for its users, a “factory pattern” is usually introduced. Users simply interact with the factory to get a copy. For example, Gnosis Multisig Wallet has a factory. So, instead of copy-and-paste the source code to Remix, compile, key in some parameters, and deploy it by yourself, you can just ask the factory to create a wallet for you since the contract code has already been on-chain.

The problem is: we need standalone contract instances for each user, but then we’ll have many copies of the same bytecode on the blockchain, which seems redundant. Take multisig wallet as an example, different multisig wallet instances have separate addresses to receive assets and store the wallet’s owners’ addresses, but they can share the same program logic by referring to the same library. We call them ‘proxy contracts’.

One of the most famous proxy contract users is Uniswap. It also has a factory pattern to create exchanges for each ERC20 tokens. Different from Gnosis Multisig, Uniswap only has one exchange instance that contains full bytecode as the program logic, and the remainders are all proxies. So, when you go to Etherscan to check out the code, you’ll see a short bytecode, which is unlikely an implementation of an exchange.

0x3660006000376110006000366000732157a7894439191e520825fe9399ab8655e0f7085af41558576110006000f3

What it does is blindly relay every incoming transaction to the reference contract 0x2157a7894439191e520825fe9399ab8655e0f708by delegatecall.
Every proxy is a 100% replica of that contract but serving for different tokens.

The length of the creation code of Uniswap exchange implementation is 12468 bytes. A proxy contract, however, has only 46 bytes, which is much more gas efficient. So, if your DApp is in a scenario of creating copies of a contract, no matter for each user, each token, or what else, you may consider using proxy contracts to save gas.

2. Why use EIP1167

According to the proposal, EIP is a “minimal proxy contract”. It is currently the known shortest(in bytecode) and lowest gas consumption overhead implementation of proxy contract. Though most ERCs are protocols or interfaces, EIP1167 is the “best practice” of a proxy contract. It uses some EVM black magic to optimize performance.

EIP1167 not only minimizes length, but it is also literally a “minimal” proxy that does nothing but proxying. It minimizes trust. Unlike other upgradable proxy contracts that rely on the honesty of their administrator (who can change the implementation), address in EIP1167 is hardcoded in bytecode and remain unchangeable.

That brings convenience to the community.

Etherscan automatically displays code for EIP1167 proxies.

When you see an EIP1167 proxy, you can definitely regard it as the contract that it points to. For instance, if Etherscan finds a contract meets the format of EIP1167, and the reference implementation’s code has been published, it will automatically use that code for the proxy contract. Unfortunately, non-standard EIP1167 proxies like Uniswap will not benefit from this kind of network effect.

3. How to upgrade a contract to EIP1167 compatible

*Please read all the steps before use, otherwise there might have problems.

A. Build a clone factory

For Vyper, there’s a function create_with_code_of(address)that creates a proxy and returns its address. For Solidity, you may find a reference implementation here.

function createClone(address target) internal returns (address result){ bytes20 targetBytes = bytes20(target); assembly { let clone := mload(0x40) mstore(clone, 0x3d602d80600a3d3981f3363d3d373d3d3d363d73000000000000000000000000) mstore(add(clone, 0x14), targetBytes) mstore(add(clone, 0x28), 0x5af43d82803e903d91602b57fd5bf30000000000000000000000000000000000) result := create(0, clone, 0x37) }}

You can either deploy the implementation contract first or deploy it with the factory’s constructor. I’ll suggest the former, so you can optimize it with higher runs.

contract WalletFactory is CloneFactory { address Template = "0xc0ffee"; function createWallet() external returns (address newWallet) { newWallet = createClone(Template); }}

B. Replace constructor with initializer

When it comes to a contract, there are two kinds of code: creation code and runtime code. Runtime code is the actual business logic stored in the contract’s code slot. Creation code, on the other hand, is runtime code plus an initialization process. When you compile a solidity source code, the output bytecode you get is creation code. And the permanent bytecode you can find on the blockchain is runtime code.

For EIP1167 proxies, we say it ‘clones’ a contract. It actually clones a contract’s runtime code. But if the contract that it is cloning has a constructor, the clone is not 100% precise. So, we need to slightly modify our implementation contract. Replace the constructor with an ‘initializer’, which is part of the permanent code but can only be called once.

// constructorconstructor(address _owner) external { owner = _owner;}// initializerfunction set(address _owner) external { require(owner == address(0)); owner = _owner;}

Mind that initializer is not a constructor, so theoretically it can be called multiple times. You need to maintain the edge case by yourself. Take the code above as an example, when the contract is initialized, the owner must never be set to 0, or anyone can modify it.

C. Don’t assign value outside a function

As mentioned, a creation code contains runtime code and initialization process. A so-called “initialization process” is not only a constructor but also all the variable assignments outside a function. If an EIP1167 proxy points to a contract that assigns value outside a function, it will again have different behavior. We need to remove them.

There are two approaches to solve this problem. The first one is to turn all the variables that need to be assigned to constant. By doing so, they are no longer a variable written in the contract’s storage, but a constant value that hardcoded everywhere it is used.

bytes32 public constant symbol = "4441490000000000000000000000000000000000000000000000000000000000";uint256 public constant decimals = 18;

Second, if you really want to assign a non-constant variable while initializing, then just add it to the initializer.

mapping(address => bool) public isOwner;uint public dailyWithdrawLimit;uint public signaturesRequired;

function set(address[] _owner, uint limit, uint required) external { require(dailyWithdrawLimit == 0 && signaturesRequired == 0); dailyWithdrawLimit = limit; signaturesRequired = required; //DO SOMETHING ELSE}

Our ultimate goal is to eliminate the difference between runtime code and creation code, so EIP1167 proxy can 100% imitate its implementation.

D. Put them all together

A proxy contract pattern splits the deployment process into two. But the factory can combine two steps into one, so users won’t feel different.

contract multisigWallet { //wallet interfaces function set(address[] owners, uint required, uint limit) external;}contract walletFactory is cloneFactory { address constant template = "0xdeadbeef"; function create(address[] owners, uint required, uint limit) external returns (address) { address wallet = createClone(template); multisigWallet(wallet).set(owners, required, limit); return wallet; }}

Since both the factory and the clone/proxy has exactly the same interface, no modification is required for all the existing DApp, webpage, and tools, just enjoy the benefit of proxy contracts!

4. Drawbacks

Though proxy contract can lower the storage fee of deploying multiple clones, it will slightly increase the gas cost of each operation in the future due to the usage of delegatecall. So, if the contract is not so long(in bytes), and you expect it’ll be called millions of times, it’ll eventually be more efficient to not use EIP1167 proxies.

In addition, proxy pattern also introduces a different attack vector to the system. For EIP1167 proxies, trust is minimized since the address they point to is hardcoded in bytecode. But, if the reference contract is not permanent, some problems may happen.

You might ever hear of parity multisig wallet hack. There are multiple proxies(not EIP1167) that refer to the same implementation. However, the wallet has a self-destruct function, which empties both the storage and the code of a contract. Unfortunately, there was a bug in Parity wallet’s access control and someone accidentally gained the ownership of the original implementation. That did not directly steal assets from other parity wallets, but then the hacker deleted the original implementation, making all the remaining wallets a shell without functionality, and lock assets in it forever.

https://cointelegraph.com/news/parity-multisig-wallet-hacked-or-how-come

Conclusion

In brief, the proxy factory pattern helps you to deploy a bunch of contract clones with a considerably lower gas cost. EIP1167 defines a bytecode format standard for minimal proxy and it is supported by Etherscan.

To upgrade a contract to EIP1167 compatible, you have to remove both constructor and variable assignment outside a function. So that runtime code will contain all business logic that proxies may need.

Here’s a use case of EIP1167 proxy contract: create adapters for ERC1155 tokens to support ERC20 interface.

pelith/erc-1155-adapter

References

https://eips.ethereum.org/EIPS/eip-1167
https://blog.openzeppelin.com/on-the-parity-wallet-multisig-hack-405a8c12e8f7/

Donation:
pingchen.eth
0xc1F9BB72216E5ecDc97e248F65E14df1fE46600a

Reason Why You Should Use EIP1167 Proxy Contract. (With Tutorial) was originally published in Taipei Ethereum Meetup on Medium, where people are continuing the conversation by highlighting and responding to this story.

👏 歡迎轉載分享鼓掌

Trong video này, tớ sẽ điểm danh các sản phẩm dưỡng thể cần thiết trong tủ và review một số sản phẩm đã sử dụng.

Các sản phẩm được nhắc đến trong video:

SỮA TẮM
- Bioré dưỡng ẩm mềm mịn hương Hoa anh thảo
- Naive hương đào
- The Body Shop Piñita Colada shower gel
- Cathy Doll Jejju Raining shower gel
- The Body Shop Vanilla Chai shower gel

TẨY DA CHẾT
- The Body Shop British rose exfoliating gel body scrub
- The Body Shop Piñita Colada Smoothes and refines skin

SHAVING LOTION (kinda)
- Yves Rocher après shampooing lissant 48h
- Cathy Doll 99% Aloe Vera & Snail

DAO CẠO
- Gilette Vector
- Gilette Mach 3 (highly recommend!)

DƯỠNG THỂ
- Aroma Magic Honey & Shea Butter Body Lotion
- The Body Shop Piñita Colada body butter
- Tokio Milk Mimosa & Mandarin soothing body lotion
- Thann Body butter with Cocoa butter, Licorice and nano Shiso extract

CHỐNG NẮNG (phần này tớ quên nhắc đến)
- Nivea Sun moisturising sun lotion SPF 50 PA++:
khả năng chống nắng khá tốt, chất kem lỏng và dễ tán, có nhũ trong kem.

-----------------------------------------------------

Blog:
http://karedlipstick.blogspot.com/

Facebook page:
https://www.facebook.com/karedlipstick

Instagram: http://instagram.com/karedlipstick
Snapchat: karedlipstick

Magician uses chicken nugget to find her card!
P.S. I almost choked during this performance lol. Do not recommend eating nugget and talking at the same time.

Like the cards used in this video? Grab them now only at: www.patrickkun.com

To watch the latest magic videos, be sure to follow me on social media below:

Instagram: @patrickkun
Youtube: http://www.patrickkun.com/youtube
Facebook: http://www.facebook.com/patrickkunmagic
Twitter: http://www.twitter.com/patrickkunmagic
Visit me: http://www.patrickkun.com

Such a blast performing for these folks at the Cape Town International airport. Her signed card vanished from the deck and reappeared inside of a beer bottle. Priceless reactions! This is why I do what I do.

Like the cards used in this video? Grab them now only at: www.patrickkun.com

To watch the latest magic videos, be sure to follow me on social media below:

Instagram: @patrickkun
Youtube: http://www.patrickkun.com/youtube
Facebook: http://www.facebook.com/patrickkunmagic
Twitter: http://www.twitter.com/patrickkunmagic
Visit me: http://www.patrickkun.com