Martina (@Mnext79) header
Martina (@Mnext79) profile picture

加密|Web3|Branding|PR 记录下一代金融基建产品从 1到100 关注品牌设计、产品体验、市场洞察 也分享工作之外的生活

Hong Kong
Joined October 2026
Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)Photo by Martina (@Mnext79)
链上钱包,也开始照顾社恐了。 Crossmint 11月17日介绍:法币购买的USDC、EURC可直达Solana上的Helius加密余额,需先有相应私密钱包。初版入金地址、币种、金额仍公开,后续对手方地址也可见。 先撤掉“余额展示台”,入口的小票还在。隐私功能的进度条,原来这么具体。 crossmint.com/announcement/c… #Solana #Web3
11
GPU也开始聊“下个月多少钱一小时”了。 Akash 11月17日公布Compute Forwards设计:提前锁定未来月份的GPU小时价格,合约设计以真实算力交付结算。目前只有设计、白皮书和模拟市场,尚未开放交易;试点还要过审计等关卡。 对做AI的团队来说,能提前算清算力账单,大概和模型跑分快一样让人开心。GPU很贵,预算表也想睡个安稳觉。 akash.network/blog/introduci… #DePIN #AI
14
企业资金上链,最后还是绕不开一句:这笔谁批的? VALR 11月17日推出VALR Business,面向企业支付、托管和资金管理。官方文档列了多用户角色权限、付款审批,以及记录谁在何时操作的审计日志。 这些功能看着没K线热闹,却很有办公室的真实感:财务终于不用在群里一层层往上翻聊天记录了。 blog.valr.com/blog/valr-laun… support.valr.com/hc/en-us/ar… #Web3
32
代币化基金也有个很现实的问题:产品做好了,谁负责把它放到客户面前? Synthesys 11月17日宣布与WisdomTree合作,首批接入货币市场、美股大盘和科技策略三只基金,已在新加坡注册为受限计划,通过受监管渠道面向合资格投资者。 值得看的是分销连接:银行、券商不用每家从头搭一遍接口。基金有了链上版本,也得有人把路修到用户门口。 prnewswire.com/news-releases… #RWA
35
交易所的产品经理,最近连收款页面也卷上了。 OpenPayd 11月17日宣布,向Gate更多业务实体扩展英镑账户和欧元SEPA支付能力,支持Gate Money。新消息是支付基础设施扩容,产品本身10月已上线。 比起首页又多一个入口,我更想看费用和到账时间能不能一眼说明白。钱在路上的时候,谁都不想做阅读理解。 openpayd.com/announcements/g… #Crypto
29
币圈最隐形的成本,是你明明没交易,却像上了一整天班。 看盘、翻公告、查钱包、围观群聊。 手机放下了,脑子还挂着限价单。 别人问:“今天赚了吗?” “没有,今天主要负责理解市场。” 建议交易软件增加一项: 本周研究时长,折合多少杯奶茶。 你们一天里,真正在下单的时间有多少? #Crypto #Web3
1
52
应援棒和现金流,居然坐到了一桌。 Astar今天介绍了Soneium首个K-pop IP Bond,关联演唱会收入,面向合资格用户;钱包里的凭证不能交易,本息按发行条款到期支付。 这个RWA选题挺有画面:台上唱安可,台下有人研究到期日。娱乐和金融的交集,突然变得很具体。 astar.network/blog/soneium-i… #RWA
37
看黄金的功课又多了一页。 PancakeSwap今天介绍了Base上的PAXG/USDC池。买金之外,还能提供流动性收手续费,也得承担价格波动和无常损失。 以前研究金价,现在还要研究区间。金子没变,打开它的方式越来越像上班了。 nitter.cf/PancakeSwap/status/212… #RWA
Gold looking pretty good here 🧈 PAXG/USDC pool is now live on PancakeSwap @base 🥞 Add liquidity and earn on $PAXG, gold tokenized by @Paxos. 👉 link.pancakeswap.finance/pax…
2
39
公司买比特币,也有“小份加购”。 Capital B 11月17日公告:新买4枚BTC,花费约27万欧元,其比特币储备策略下的持仓增至3,554枚。 看惯了几千枚的大单,突然看到4枚,有种公司财务拿着购物清单说“这次先补一点”的画面感。金额不大,公告倒是一本正经。 actusnews.com/en/download/ca… #BTC
32
看行情的那只小壁虎,也想把交易接上了。 CoinGecko 11月17日宣布获得Solana Foundation支持,将扩展数据和研究工具,并探索交易功能,现有网站、App和API照常运行。 我想看它怎样把报价、费用和风险提示排进同一页。少开几个窗口的快乐,币圈人应该懂。 coingecko.com/learn/next-cha… #Web3
31
跨链基础设施,也开始交收入作业了。 StablecoinX 11月16日披露:Q3营收约47.8万美元,主要来自跨链验证节点服务;同期营业亏损约193.1万美元。 我更好奇后面的复购:跨链量增长时,有多少会变成持续付费的需求?技术跑通之后,收入表也得跟着跑。这个行业的“基建”,可以多聊一点具体生意。 globenewswire.com/news-relea… #Web3
21
连接钱包这一步,机构版还带着审批流。 WalletConnect 11月16日公布Utila认证案例:机构可用原钱包接入DeFi,交易请求仍经过审批、白名单和额度规则,签名后留有审计记录。 这个细节挺实在:业务想少跳几个页面,财务想知道谁点了确认。两个愿望,终于能放进同一个流程里。 walletconnect.com/blog/utila… #DeFi
14
Backpack这次的更新,写在牌照里。 11月16日官方宣布美国交易与清算业务获CFTC批准,涵盖DCM与DCO;计划提供全天候杠杆永续、全仓保证金与全球统一订单簿。获批和正式开盘,分开看。 我最想看统一盘口落地后的深度和滑点。交易页面可以很热闹,下单那一下最好很安静。 learn.backpack.exchange/blog… #Crypto
17
ETHFI也去日常金融App里串门了。 ether.fi今天凌晨宣布:ETHFI已在Revolut的欧洲经济区和英国App上线。 我对这种入口变化还挺好奇:用户先在熟悉的App里认得一个代币,之后会不会去了解它背后的协议?上架是见面,真正用起来才算认识。 nitter.cf/ether_fi/status/212237… #ETHFI
ETHFI is live on @Revolut app in EEA and UK Over 80M users across in over 40 countries are seeing ETHFI for the first time It won’t be the last
41
银行的钱,也开始赶周末的进度了。 DBS 11月16日宣布与摩根大通Kinexys打通代币化存款网络,机构可在美、新两地链上美元账户间全天候转账,蚂蚁国际首用。 这是许可链上的银行存款,传统账户出入金仍有周末维护窗口。让我更感兴趣的是:财务少等一个周一,链上的用处就具体了一点。 dbs.com/newsroom/DBS_and_Kin… #Tokenization
1
1
41
INFI这次是“先送到,再开门”。 infiniFi公告:空投16日开始分发,到账时暂不可转账;计划今晚(11月17日)北京时间23:30,在以太坊和Base同步解冻。 原来“钱包里看得见”和“已经能转”,中间还隔着一张时间表。今晚更想看看开门后的流动性。 nitter.cf/infiniFi/status/212235… #DeFi
94
CPOOL换工牌,交易日历也得跟着换。 Bybit公告:11月18日北京时间16:00停止CPOOL/USDT交易并取消挂单,支持1:1换为CLEAR;新交易对计划20日16:00开放,时间可能调整。 名字一换,搜索框、挂单、交易时间都得对表。看K线之外,又多一份日历管理员的工作。 announcements.bybit.com/en/a… #DeFi
60
手机在充电,猫在等你回消息。 蓝V朋友来串个门,聊加密也行,发猫图也行。 今天主打一个:认识新朋友🐾 #蓝V互关 #猫猫
103
64
1,127
V神这次的“看多”,看多的是数学。 11月16日,他转向支持leanPCS:希望更快推进签名与证明聚合,减少后量子签名变大带来的链上负担。相关EIP-8288仍是草案,没有确定上线时间。 别人在算涨几个点,底层在算未来签名太大怎么装。以太坊连行李额度都提前研究上了。 nitter.cf/VitalikButerin/status/… #ETH
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: ethresear.ch/t/sphincs-minus… If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: vitalik.eth.limo/general/202… ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. firefly.social/post/x/212092…
1
1
59
链上隐私,也可以先给余额装个窗帘。 WBTC 11月16日介绍的Zama机密金库,会加密个人存取金额和份额余额;地址、时间戳、汇总数据仍公开。若一批只有一人,汇总金额也可能暴露那笔存款。 账能核,钱包也想留点私人空间。“窗帘挡住哪一面”,比隐私标签更有意思。 globenewswire.com/news-relea… #DeFi
40