bc-bizdev
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- robots: noindex, nofollow --- # #SmartCustody for NFTs ###### tags: `article / in process` #SmartCustody is a risk-modeling system that assesses risk as the consequence of a vulnerability being exploited multiplied by the likelihood of that vulnerability being exploited, with the consequence usually (but not always) focused on the loss of an asset. It then assesses resolutions for those risks per their difficulty, which can be based on cost or on loss of functionality. Different assets have different risk models and require different scenarios for protection. The original #SmartCustody focused on protecting Bitcoin-based digital assets, while this document focuses in NFTs. Ethereum would be a different scenario, closer to NFTs than to Bitcoin. ## Asset Identification To fully risk model NFT holdings requires answering portfolio questions to create a better understanding of the assets, their valuation, and their functionality. This allows assessment of both the consequences of lost and the costs of resolution. Initial questions include: 1. What is the overall value of the portfolio? 2. What is the average value for individual NFTs within the portfolio? * Low-value portfolios may receive insufficient returns from a #SmartCustody model. * High-value NFTs and high-value portfolios consisting of lower value NFTs may require different models. 3. What is the public awareness of the NFTs? * Particularly high publicity NFTs, such as the Bored Apes, can create unique threats. 4. How frequently are the NFTs traded? * NFTs that are not frequently traded have the option to be better protected. 5. Is the account holding your NFTs used for other activities requiring cryptographic authentication or private keys? * Other functionality increasingly creates a honeypot that could make it a target (and which could increase your losses). 6. Are the NFTs regularly viewed? By yourself? By others? * NFTs stored as an investment can also be better protected. * There may be different models for NFTs that are individually and publicly viewed. 7. Is there a need for some or all of the NFTs to be publicly linked to their owner? * NFTs linked to a real-world identity can create new vulnerabilities. 8. Is there a need for some or all of the NFTs to be linked together? * Maintaining numerous NFTs on the same Ethereum address can also create a honeypot. 9. Do the NFTs have functionality other than artwork? * NFTs already exist with functionality such as Discord access; use of functionality such as this may require different storage mechanisms. By answering these questions, you will be able to create a personal strategy for protecting NFTs that will likely not fix everything, but that will help you fix the problems most likely to affect you with the solutions most likely to have strong impact and least likely to have strong consequences on the functionality that you count on. __Do _not_ answer these questions here or in a Google Doc. These are questions that should be personally asked and discussed to create a #SmartCustody strategy; they are too revealing to be placed in a public location.__ ## Ethereum Vulnerabilities Risk in #SmartCustody is determined by brainstorming specific vulnerabilities for asset holding ("custody vulnerabilities"), asset transfer ("interface vulnerabilities"), and other issues ("non-physical vulnerabilities"). This is often a personal process based on an individual's cryptocurrency processes, their concerns, and their risk adversity. However, the architecture, technology, and culture of the Ethereum community also create unique vulnerabilities, some of which are associated with new Adversaries, not currently outlined in the #SmartCustody book. The following Ethereum vulnerabilities should at least be considered by any NFT holder. 1. Everything I own can be seen together. * Adversary: Correlation Ethereum generally promotes a culture of one key for one user. Wallet technology generally links a single key-pair to an account. SmartContract technology often requires currency and assets to be held on the same account. Altogether this creates a situation where everything that someone owns can be linked to a single Ethereum address, allowing easy correlation. This can be a much more dangerous type of correlation than that assumed by the Correlation adversary in #SmartCustody. It's not just that different funds can be linked together, but ... everything can. 2. If I lose one key, I lose everything. * Adversary: Centralization (New) This is a new adversary, currently missing from #SmartCustody, and more problematic on Ethereum. A single private key tends to be used to unlock personally held funds, to access smart contracts, and to create signatures. If that private key is lost or stolen then all functionality goes with it. 3. Everything I own could be stolen together. * Adversary: Network Attack, Personal #SmartCustody for Bitcoin generally assesses personal network attack as a low risk. Sophisticated hackers are more likely to go after exchanges or corporations, not individual asset holders. (Obviously, individual holders may have different risk assessments for their own holdings.) That general rule may not be true for Ethereum, where honey pots of assets and funds are created due to the use of singular Ethereum addresses, as discussed in the Correlation and Centralization adversaries. This situation can be made even worse by high-profile NFTs with known, high values. Tracing such an NFT to its address could easily lead a hacker to an individual with considerable Ethereum holdings. The huge scope of this problem can be seen in DAO treasuries, some of which have been recorded to hold billions of dollars of value. 4. I could be tricked into giving up permissions. * Adversary: Social Engineering Social engineering is a high-level threat for many digital assets, but it's a particular problem for Ethereum, again due to a combination of culture and technology. The technological issue comes from wallets such as MetaMask that aren't sufficiently clear (or which don't offer sufficiently strong warnings) about what permissions are being given away. The culture issue comes from common-place airdrops, some of which require no permissions, some of which require permissions to receive, and all of which require permission to transfer. A combination of poor UI design for permissions and devious use of airdrops has already created real losses of funds and assets, usually when people gave away access to their funds while accepting an airdrop. 5. It's expensive for me to be safe. * Adversary: Cost (New) Optimal digital asset protection usually requires moving those assets into cold storage when they're not being used and moving them back to a warm wallet when they're ready to be traded. Another method of protection is to use multisigs. Unfortunately, most of these fundamental security measures are currently costly on the Ethereum network due to gas fees. Moving funds to or from cold storage can easily cost $100 each way, while these fees can be even higher if activation of a Gnosis smart contract is required due to use of a multisig. This not only limits _when_ #SmartCustody can be used, but it also increases users' reluctance to do so because of the costs. (This is another new adversary, first identified on the Ethereum network.) 6. NFTs may reveal my personal information. * Adversary: Exposure (New) NFTs are still a raw technology and have unique privacy issues related to the fact that the blockchain record of an NFT often links to a URL to display the actual image. The web servers powering those URLs can access unexpected information about a user such as their IP address, which creates new Exposure risks not found in standard cryptocurrency usage. Related to this is a recent "hack", where a user created an NFT that displayed in different ways depending on where it was accessed from; this underlies the possibility of IP exposure (and there's more than that, as web browsers also tend to collect information related to machines and browsers being used).

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully