#AMA: Web3 Security by YZi Labs

YZi Labs Subscribe Podcast 1h 0m 0 downloads Added 2026-11-16 #Trending

Listen Preview

00:00
1:00:27

Listen the full audio for free - sign up to download, transcribe and summarize.

Listen without signing up - 3 free downloads per day - includes AI transcript, summary and SRT Sign up free →

AI Summary

Binance 专家在 AMA 中深入探讨 Web3 安全格局,强调安全应成为项目全员的首要优先事项,并分享了 MPC 钱包、智能合约审计等基础设施实践。 - Web3 带来了新型安全威胁,Binance 希望通过分享洞察帮助项目应对漏洞、帮助用户掌控身份与数据。 - 本次 AMA 分三部分:Binance 技术与安全团队概述 Web3 安全格局及 Binance 的举措、与三个 Web3 安全项目专家的小组讨论、回答听众问题。 - Binance 在安全基础设施上投入大量研发,采用基于 MPC 的多签钱包管理系统,并构建了 Binance 的安全体系。 - Binance 安全负责人 Gemis 团队在智能合约审计、自动化扫描和风险评分方面做了大量工作。 - 当前主要挑战包括:域名劫持与注册商社会工程攻击、基础 ID 基础设施安全、智能合约代码漏洞、私钥管理与团队治理内控。 - 核心经验一:安全需要全员参与,IT、安全、工程、业务运营乃至产品团队都应达成共识,把安全视为项目成功的"零号优先事项"。 - 核心经验二:Bob 与 Gemis 曾作为小组成员参与大量其他项目的安全评估,积累了跨项目经验。 建议项目团队立即将安全纳入全员共识与开发流程,从域名、合约代码到私钥管理逐层排查风险。

Want this audio offline?

Download the original M4A - AI transcript & summary included - 3 free per day

Transcript

Hello everyone, thank you so much for joining us for our AMA session today. We're so happy to see you all here. In today's one, our session will take a deep dive into Web3 security. And as Web3 has ushered a new class of server-threat. We want to share some insights to help project better-address security vulnerabilities and help our users to better maintain control over their identities and data. And today's session will include three different segments. Use our experts from the Binance Tech and Binance security teams will give a hell-ever overview of the Web3 security landscape. And some Godreels Binance has implemented. And second, we'll have a panel discussion with three industry experts from the Web3 security project. And third, we'll answer some of the questions we have collected from our listeners. And we'll start today's session now with Bob from the Binance Tech team. Bob, I'll pass on the microphone to you first. Yeah, sure. Thank you. Thank you guys. Can you guys give me a fine? Yep. Cool. So hi, everyone. It's so nice being here to come. I'd like to have some discussion and sharing in terms of what we have. And also the journey, the events have been through that. So before we get into those details, probably we'd like to share the one-the-key things which you said in line with the Binance mission. It's actually, you know, you guys know that Binance is providing the infrastructure service to better organizing the works. They work with all here, right? So in terms of security, actually, we tried to help our Web3 project users and also those project owners to better use and allow it to balance the ecosystem and secure infrastructure services. So you can create more and more user-friendly, secure Web3 projects. And actually, Binance has been doing quite a lot of investment and also like the R&D efforts in terms of security infrastructure. One key thing is probably know that we're using like the multi-party computation based on PC, the multi-sick wallet management system. And also on top of that, we also build a Binance-Cars existence. And the gemesting has been working quite a lot on the terms that security are audit on those small-conch and with the collaboration of the other quite a lot. There's no firm left, so it's OK, as well. Gemis actually, by the way, Gemis they are security lead from Binance. And also, we've done quite a lot of small-conch, automated scanning and risk scoring for Web3 community users, etc. And that's quite a lot of other like that. Powerpound, the programs, initiatives, Gemis, things working on as well. So actually, let's start with some of the main major changes we face in today in terms of Web3 here. Then we can talk a little bit about the solutions by Binance-Cars. As you guys know, the security is so tough job to be honest. There's so many different things to think about that, particularly when you're a project and systems are getting more complex and more proper. When building a system, or a team or your existing team is doing some preparation within the communities, there are several very technical and security challenges. I can give you guys a very simple example. You guys probably heard of that several days ago, there's quite a lot like the several cases in terms of the domain hacking and the register social engineering issues. The first instance before, it costs quite a lot by the security instance and the phone loss. So how to ensure the current fundamental ID infrastructure like domain or maybe just current networking environments could be very key thing to make sure they're very good from the foundation layer for the security here. And just moving a little bit up layer, how to minimize the potential is far out of the box on smart contract log in the code, which is also very critical here. And last but not least, like the quality and the farm management, particularly on those the private key management and the governance and internal controls on the push and teams, those things are very, very critical as well. So we've been through the journey and we're trying to still, at this point, we're still trying to tackle various security challenges. Some of the key experience I'd like to share with you guys. Number one thing, I think really just before getting into some like the tactical solutions etc. One of the key things is make sure all the team members can be onboarded for security. It's so important for me to make sure everyone, including your IT team, your security team, of course, is their job, of course, but security is not just job for the security team like the engineering team and your business operation team. Even the product team need to be part of that. So make sure everyone's on the same page and understand this security is really priority zero staff for the project success because this is so fundamental stuff here. Second priority is actually by looking into the past several years, Jimi and I was working for a panelist on quite a lot of other projects in terms of security and also like the Web 3 project within reviewing and also working together. There are some best players by just absorbing those failures. One of the key things is we just kind of identify a developer's size to keep identifying the weakest link of a system. 13 operations in a regular basis. Some of the things I mentioned before are the IT domain vendor or the car computing infrastructure vendor. You build something on top of that, right? So how to make sure those basic management, the permission management is good enough. And also how to make sure your operation team, they don't get granted the excessive permissions, always get the least permission based on the job scope and responsibilities. An awful review of the system, the team, a regular basis, also the key purpose to improve the security here. And the earlier you're doing this, the more benefit the team and your users working. So one of the key concepts here is really just identify the weakest link of a system on operations. We've seen some projects that actually they're using a very good amount of solution, but also very good audit, etc. But eventually they just fail some very basic start-led domain name stuff as we discussed before. Some of the very good projects they are working so hard on smart contracts, security, but actually they just failed at the private key management. We've seen like some of the gaming company, they just, the founders just failed to manage the key and eventually lost the quite lot of funds. The last thing I like to share here is actually in terms of the attack space. One of the key things here is actually in order to make sure that the project assistant just with a more secure compared to other projects, one of the key things is minimize the attack space. So make sure every various aspects can be limited with this exposure to their son-of-world. And the internal within the team probably, like some of the key security principles need to be developed within the engineering team, developers, and also operation teams, like the digital basis. Some of the development teams within the team, they probably only need to understand public code here. And some of the guys they touch the production environment usually, I know some of the teams they're working at the early stage, but make sure those emissions can be fully isolated based on the national basis and also their trust solution here. So along with that, Binance also gave several key security infrastructure service products for the web-driven communities. One thing I mentioned before is about the NPC based Binance Custy products is key to have the project owners to manage those properties and also the firms in a very secure way. And also, we are working quite a lot in terms of the security audits internally externally. And also, we've done quite a lot in terms of the post-hats port by our detecting and executing. And we also developed a lot of land-based solution on the risk of calling a sector on the AMP-P chain. So there's some of the kind of the high level sharing here that we can discuss more details in the later panel discussion as well. Jimmy, want to continue on the discussion here? Oh, yeah, thanks, Bob. Yes, the Web-3 threat landscape is evolving rapidly. Fred actors choose the most economical and efficient ways to attack. Many Web-2 threats continue to be effective in Web-3, including fishing, seam-swipe, malware payload and Bob attacks. In fact, more than 50% of the incidents we saw in the past year across major blockchains are due to Web-2 vulnerabilities. One recent example is the Type-R-Swipe pack, where the Google Tag Manager, GTM, was compromised and the hacker inserted a malicious smart contract into the front end. GTM has an option for inserting custom JavaScript code. This is a very powerful functionality, and GTM users need to use throw-based access control to tame it. Who's for the developer, the security checker and the publisher should be separated, so that no single person can publish custom code on his own? Fishing is a low-cost and effective way to exploit the weakest link in the chain, which is the human itself. When something sounds too good to be true, it normally is. One of the biggest hacks of the year was the 620 million one at Axi Infinity. The fishing in this case was very targeted. The hackers scour Linkin for Axi Infinity employees with special access. They found a deaf-up engineer and engaged him on a fake job interview. The job offer file contained malware, and when the deaf-up engineer opened the file on his company laptop, the hacker came away in. From there, the hackers were able to compromise sufficient number of validator nodes to steal the funds. Water security, Bob mentioned earlier, is part of the basic security hygiene in Web3, and also is the most important one. The hardest thing for beginners is to maintain their private keys in a safe way. Users should maintain both a hot wallet and a cold wallet. For tokens and entities with significant value, they should be swept to the cold wallet. If running a cold wallet is too cumbersome for you, sending the valuable tokens and entities to a weaponable centralized exchange would be safer than keeping them on in a hot wallet. One of the things to remember is never to back up your wallet app to iCloud. The backup would contain the private keys and your funds' safety would fall back to how safe your iCloud account is. Users often want to phone more into new DeFi projects or NFT projects. You should always use a burner wallet with minimal funds for this. This way, even if you fell for a...

Finished reading? Take the audio and transcript with you

Download the audio plus timestamped transcript and SRT subtitles · RSS

Frequently Asked Questions

What is this Space about?

"#AMA: Web3 Security by YZi Labs" is a live audio conversation on X (Twitter) hosted by YZi Labs1h 0m. Download the audio via IFY Hub to get AI transcript and summary of the discussion.

How do I download this Space's audio?

Click the "Download Now" button (3 free downloads per day after registration). Our system parses and downloads the audio automatically, then generates AI transcript and summary.

How long is this Space? Is it worth listening to?

This Space is about 1h 0m, hosted by YZi Labs. Preview it for free, then download the full audio and AI summary if you like it.

More Hot X Spaces

View all

#映画たんプリスタッフトーク延長戦

Transcript

本作《电影 光之美少女 奇迹跳跃》相关访谈中,上田、矢野等主创回顾了剧本创作与制作幕后,强调角色设计与团队协作让作品充满情感与惊喜。

tian returns! sfw chats

Transcript

这是成年内容创作者(“puppy”)在直播中与观众Jay互动,解释拉黑原因(因嗨后易被冒犯),并完成乳头夹与打屁股(左右各6/7下)等BDSM惩罚任务。

~Tian~ 3h 31m

Bitcoin and Stocks: Q4 Dump

Transcript

Ben 与听众 Mitch 讨论比特币后市策略:他基于自设指标判断当前或非周期高点,预期 2027 年迎来牛市,并计划在可能的夏季低点(约 6 万–6.3 万美元)分批建仓。

Foolinlove&copterbank

Transcript

两位剧迷复盘泰剧《Foyin Love》第七集:片头从红变蓝、剪辑与配乐精心设计,盛赞主演Po的演技与导演巧思,并讨论后续剧情走向及演员来华见面会的安全担忧。

Bitcoin Q4 2026

Transcript

比特币交易者 Ben 与 Zach 讨论比特币中期选举后的弱势窗口和潜在低点,并探讨机构化后“无狂欢式”牛市是否成为新常态。

#alkanSHEA #NoToPaxSilica SHEASHELLS: 3,873

Transcript

这期播客是几位主播用菲律宾语/多语夹杂闲聊,讨论PBB(Pinoy Big Brother)节目里的“Shey Shale”和“Cheya”等话题,还提到即将到来的惊喜嘉宾、11月29日周年庆和圣诞派对安排,以及是否参加下周活动的犹豫。

【Take2】CZと語るAMA

Transcript

CG5(赵长鹏)在日文活动中介绍自传《币安人生》(“Speak”相关书名),谈日本与币安的渊源,呼吁日本Web3创业者继续建设。

AI AND DEFENSE TALK WITH GLOBAL X ETFs | STOCK MARKET TALK

Transcript

美股交易员Mike和Brian讨论了CPI数据超预期但同比指引缺失引发的市场负面反应、政府停摆影响以及英伟达等Mag 7个股走势,认为当前市场缺乏动能、不宜追涨,建议多数投资者观望等待周四关键K线的方向确认。

About this Space

"#AMA: Web3 Security" is a trending podcast Space on X (Twitter) hosted by YZi Labs, about 1h 0m long. With IFY Hub, you can download the full audio for free and use AI to auto-generate transcripts and summaries - perfect for reviewing, quoting or sharing key moments.

How to Download

  1. Click the "Download Now" button above
  2. Our system parses and downloads the audio automatically
  3. AI transcript and summary are generated after completion
  4. View or re-download anytime from your history