Ko-Wei Tseng
    • Create new note
    • Create a note from template
      • 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
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
      • Invitee
    • Publish Note

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

      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.
      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
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Engagement control 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
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
Invitee
Publish Note

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

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.
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
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# IOTA的歷史 感謝大熊的蹤跡提供(https://www.iota.love/) ## IOTA 白皮書之前的故事(2012~2015) Cfb先是做了BCNEXT,然后做了NXT,依然失败了,不过在这个项目中实现了纯POS的共识。 [权益证明机制PoS的演变:从Peercoin和Nxt到以太坊_区块](https://www.sohu.com/a/409422280_100217347) **1、2012年 Cfb宣布Qubic(Quorum-Based Coin),即IOTA项目的前身,在这个帖子里面,CfB提到了一些IOTA网络的一些特征。;**(后来Qubic这个单词被IOTA基金会拿来作为支持智能合约的版本代号,但随后也随着Jinn的流产而放弃了) [Qubic - Quorum-Based Coin](https://bitcointalk.org/index.php?topic=112676.0) 2、**David认识了Cfb,两人进行了很多次沟通,后来对边缘计算和三元计算有了共识,组建了Jinn Labs(2014年)**。Jinn就是三元微处理器的名称。 针对三元计算处理器所配套的软件和网络基础层,产生了IOTA这个项目动机而IOTA由IOTA基金会来进行支持。 **后面认识了Popov,让他开始撰写白皮书;** 而David和Dominic项目合作多年,于是把他也拉了进来。 David Sonstebo创立基金会; ## 正式啟動(2015-2018) **3、2015年10月, Cfb在bitcointalk上发帖首次介绍了IOTA。** [IOTA bitcoin talk](https://bitcointalk.org/index.php?topic=1216479.0) **4、2015年11月25日 从社区筹集资金50万美元的BTC;** [IOTA Crowdsale](https://bitcointalk.org/index.php?topic=1262688.0) 相关人员: [Eric Wall](https://twitter.com/ercwl) 又爱又恨的冤家 **[Emin Gün Sirer](https://twitter.com/el33th4xor)** avalanche创始人——指控IOTA抄袭的人 Ralf rottmann——前期董事会成员,口碑极佳,离开后不再关注IOTA [Welcome Ralf Rottmann to the IOTA Foundation](https://blog.iota.org/welcome-ralf-rottmann-to-the-iota-foundation-157c86011438/) **5、2017年,随着那一拨牛市,IOTA币价达到了历史最高位的5块多美金,市值排名最好的时候冲到了第四名。** # 第二部分:衝突(2018-2020) ## 2.1 路线之争 1、三元与二元之争 2、去协调器方案之争(共识算法) 3、智能合约方案之争 Cfb **CFB加入IOTA基金会的公告(2018-08-14)** [Welcome Sergey Ivancheglo to the IOTA Foundation Board of Directors](https://blog.iota.org/welcome-sergey-ivancheglo-to-the-iota-foundation-board-of-directors-2167ca99e495/) **2019年6月26日,CFB从基金会辞职。** [Sergey Ivancheglo departs from the IOTA Foundation](https://blog.iota.org/sergey-ivancheglo-departs-from-the-iota-foundation-d2d9c1c61db6/) David的表态 [Letter to the IOTA community](https://medium.com/@DavidSonstebo/letter-to-the-iota-community-76c940cbc315) Cfb的回应 [My side of the story about parting ways with David Sønstebø](https://medium.com/@comefrombeyond/my-side-of-the-story-about-parting-ways-with-david-s%C3%B8nsteb%C3%B8-ab8d2c103c37) 牵涉到针对于Cooridicide的不同路线之争,另外Cfb在网络上的不当行为,以及在基金会的协作问题。 CFB加入IOTA基金会的公告(2018-08-14) **Coordicide解决方案的发布** [IOTA Announces Coordicide Solution; A Distributed Ledger Technology that Removes the Barriers of Blockchain for Real-World Adoption](https://www.businesswire.com/news/home/20190528005495/en/IOTA-Announces-Coordicide-Solution-A-Distributed-Ledger-Technology-that-Removes-the-Barriers-of-Blockchain-for-Real-World-Adoption) ## 2.2 Trinity钱包事件 2020年2月12日,Trinity钱包因为集成的第三方MoonPay的代码被黑,导致部分用户的钱包被盗; IOTA基金会通过一个迁移工具,基本上挽回了客户的损失;但是也给自己的声誉造成了很坏的影响。 在币价低迷的时候,整个基金会承受了非常大的压力,不仅来自社区,也有来自财务层面的,因此会做出一些没有经过慎重考量的决策,企图挽回或讨好社区,最终结果适得其反。 [Trinity Attack Incident Part 1: Summary and next steps](https://blog.iota.org/trinity-attack-incident-part-1-summary-and-next-steps-8c7ccc4d81e8/) ## 2.3 组织主导权(企业文化)之争 2020年12月10日 David Sonstebo被基金会公开除名 David在公开场合的不当言行给基金会带来了不少公关风险。深陷与Cfb的纠纷; [IOTA Foundation parts ways with David Sønstebø](https://blog.iota.org/iota-foundation-parts-ways-with-david-sonstebo/) David针对被除名的回应 [My departure has been greatly exaggerated](https://medium.com/@DavidSonstebo/my-departure-has-been-greatly-exaggerated-765850042e89) 强调了Dominic并非IOTA的联合创始人,而只是IOTA基金会的联合创始人; 透露了Navin是2017年与David联系才加入到仅仅会里面; Serguei popov是受David和Cfb聘请来编写白皮书; # 第三部分 復興之路(2022-today) ## 3.1 对其他生态的借鉴 不再只执着于企业市场; 直接借鉴其他链的成功经验,譬如波卡,譬如Luna等。 ## 3.2 技术路线的权衡—解决如何快速实现; - 三元的暂时搁置; - 零手续费的变通(零手续费不等于零成本); - 智能合约方案的变通; ## 3.3 团队治理的规范化 - 极客文化的冲突; - 学院派的功成身退; - Dom和Hans的主导; - 团队全职化倾向; ## 3.4 资本的引入—(借力) - 资金支持; - 上所支持; - 项目经验支持; - 恰当的施压; # IOTA的价格低迷的原因 愿景(我要为谁解决他的什么问题) → 路线(用什么方法付出多少代价来实现什么样的效果) → 实现(实现的具体步骤和交付) 战略路线之一:技术路线(反复争夺) 实现出现问题(导致交付延期) 社区和潜在采用单位的信任危机 战略路线之二:市场路线 拘泥于只关注企业市场和标准化,忽略了加密货币市场的个人化和投机性,在这块的市场营销能力不及格; - 没有专门的市场营销团队; - 受限于架构,没有做事团队; # 吸引我的特质 - 愿景是符合我的想法的; - 0手续费; - 异步共识的快速确认机制; - 可扩展性; - 0通胀率; - 标准化路线,拥抱监管; - 与对手相比,价格被低估,有较大的上升空间; ###### tags: `iota`

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

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
Wallet ( )
Connect another wallet

New to HackMD? Sign up

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