小西 retweeted
三个空投
Talus代币 $US 前有锁仓的一部分可以在这里领取
multichain-app.streamflow.finance/vesting
Billions 10月31日空投释放
staking.billions.network
$TRUST 11月5日开始释放另外一半
airdrop.intuition.systems
领取WTRUST后手动转换成 $TRUST
portal.intuition.systems/wrap
10
5
24
5,897
最近认真看了下 @satcap_，不是又一个“我们要做BTC上的pump”那种口号，而是他们把发行、流动性、交易安全和隐私拆成了能具体讨论的机制。有几个设计我挺认同的。
1️⃣先说发行。每个代币固定 2100 万枚，80%（1680万）走 bonding curve，20%（420万）留着毕业后用。Power curve 起步价大概 0.17 sat/token，对应大概 3k 开盘市值，然后平滑往上走。毕业门槛是筹到 0.1 BTC，曲线自动关，切到 AMM。
这个数字和衔接方式挺清晰的，不像有些项目毕业后流动性完全看心情。
2️⃣真正戳到我的点是毕业后的流动性。
筹集到的 BTC + 预留的 420 万代币直接注入池子，LP 所有权直接转到死地址烧掉。没有 owner key，没有管理员提现函数，也没有解锁时间表。官方说“liquidity is locked forever”。
现在很多发射台最大的信任问题就是池子随时可能被抽走，这个设计至少把这个口子堵上了（当然实际还是要看链上验证）。
3️⃣交易执行他们走的是链下订单管线，不是走公开 mempool。
所以没有机器人能在 mempool 里看到你的单子然后夹你。订单按到达顺序严格串行执行，并且强制滑点保护（minTokensOut / minSatsOut），达不到就整笔回滚，还免费。
同时数据库用行锁做串行化，避免并发下的状态混乱。这个对高频交易场景还是挺关键的。
4️⃣资金安全这块，Vault 是个人 2-of-2 Taproot 地址，链上强制，不是平台口头说“我们有多签”。交易账户是内部账本（用来快速 swap 和发射），金库是链上的。敏感操作（swap、发射、提现等）必须用 BIP-322 钱包签名，绑金额、滑点、时间戳和一次性 nonce，防重放。
5️⃣另外两个特色：
Stock pairs：可以发射和真实股票挂钩的代币（比如 $TKN / NVDA），但结算全是 BTC。
Stealth Mode：公开数据里用数据库 RLS 把地址打成 Anonymous，别人看不到你的交易轨迹。只有自己登录后能看完整记录。
不是链上完全匿名，但比完全暴露强不少。
整体看，satcap 想做的是在 BTC L1 上，把固定供应 + 永久锁池 + 防夹子 + 多签金库 + 股票配对这几件事叠在一起。现在还是 invite-only，还在打磨阶段。
我比较关注的是后续金库权限、实际交易体验，以及流动性锁定能否被独立验证。你们觉得这个方向在 BTC 生态里有戏吗？
1️⃣先说发行。每个代币固定 2100 万枚，80%（1680万）走 bonding curve，20%（420万）留着毕业后用。Power curve 起步价大概 0.17 sat/token，对应大概 3k 开盘市值，然后平滑往上走。毕业门槛是筹到 0.1 BTC，曲线自动关，切到 AMM。
这个数字和衔接方式挺清晰的，不像有些项目毕业后流动性完全看心情。
2️⃣真正戳到我的点是毕业后的流动性。
筹集到的 BTC + 预留的 420 万代币直接注入池子，LP 所有权直接转到死地址烧掉。没有 owner key，没有管理员提现函数，也没有解锁时间表。官方说“liquidity is locked forever”。
现在很多发射台最大的信任问题就是池子随时可能被抽走，这个设计至少把这个口子堵上了（当然实际还是要看链上验证）。
3️⃣交易执行他们走的是链下订单管线，不是走公开 mempool。
所以没有机器人能在 mempool 里看到你的单子然后夹你。订单按到达顺序严格串行执行，并且强制滑点保护（minTokensOut / minSatsOut），达不到就整笔回滚，还免费。
同时数据库用行锁做串行化，避免并发下的状态混乱。这个对高频交易场景还是挺关键的。
4️⃣资金安全这块，Vault 是个人 2-of-2 Taproot 地址，链上强制，不是平台口头说“我们有多签”。交易账户是内部账本（用来快速 swap 和发射），金库是链上的。敏感操作（swap、发射、提现等）必须用 BIP-322 钱包签名，绑金额、滑点、时间戳和一次性 nonce，防重放。
5️⃣另外两个特色：
Stock pairs：可以发射和真实股票挂钩的代币（比如 $TKN / NVDA），但结算全是 BTC。
Stealth Mode：公开数据里用数据库 RLS 把地址打成 Anonymous，别人看不到你的交易轨迹。只有自己登录后能看完整记录。
不是链上完全匿名，但比完全暴露强不少。
整体看，satcap 想做的是在 BTC L1 上，把固定供应 + 永久锁池 + 防夹子 + 多签金库 + 股票配对这几件事叠在一起。现在还是 invite-only，还在打磨阶段。
我比较关注的是后续金库权限、实际交易体验，以及流动性锁定能否被独立验证。你们觉得这个方向在 BTC 生态里有戏吗？
0
0
2
115
小西 retweeted
The Final Battle 👀
Amazing. I love every one of you who participated. ❤️ Privacy on @ethereum is just getting started. 🔐
As the auction goes on, $P20’s FDV has reached 1.9M, up 137.5% in 24 hours.
13,592,400 $P20, about 20% of the circulating supply, has joined the auction. In just 24 hours, the seen:
📈 Floor price up 53x
📈 Average price up 73x
34 hours left. We don’t know where it will end, but people seem to be getting interested in the first pure privacy coin and privacy NFTs on @ethereum.
Auction Link: app.plabs.online/privasea/jubjub
Buy $P20 on PEX: app.plabs.online/pex
4
1
15
1,286
小西 retweeted
More than just a privacy NFT. This is where your on-chain wealth begins.
Your Data, Your Control.
🎫 Quantity: 1,665
💎 Bidding Asset: $P20 (The Private Token on EVM)
🕗 Auction starts: Oct 19, 2026, 8:00 PM (UTC+8)
⏳ Duration: 48 hours
🏁 Auction ends: Oct 21, 2026, 8:00 $P20?
🔗 Buy link: app.plabs.online/pex
What’s $P20?
$P20 is not an ERC-20 token. It’s a native private token on @monad, similar to shielded $ZEC.
5
3
20
1,697
值得关注
由Plabs发行的ETH上的隐私NFT即将进行mint了
具体如下：
1. 之前的WL可以在迁移到ETH后free mint（共计435个）
2. 公开“隐私拍卖”（共计1665）
3. 拍卖采用 $P20 做为竞拍标的
4. 竞拍所得部分销毁，比例暂未给出
5. 单地址最多竞拍1个
6. 起拍价格100个P20，持续48H
7. 10月19日20:00（UTC+8）开始
行资产迁移，P20和NFT都会在ETH主网上流通
我觉得采用 P20 竞拍挺好的：
1. P20作为协议的核心标的，本身就需要在各个环节被赋能
2. 对于持有者来说，可以将P20一部分换成总量很少的NFT，预期产生增值效应
3. 对于想参与但是又没有P20的人来说，本身就是要花钱的，用什么无所谓，但是这样可以增加P20的流动性
参与方式：
1. 对于持有者：一定要同步到P20余额显示，就可以参与竞拍了
2. 对于没有的：
▪️到 app.plabs.online/pex 购买
▪️采用新地址（这样同步数据会从当前开始）
▪️把monad上的usdc先屏蔽（app.plabs.online/privacyfi）
▪️然后就可以购买了
从项目方公布的路线图来说，是要做长久的隐私基建和隐私服务的，所以还是很值得调研的。
#ETH #MONAD #PRIVACY #ZCASH #P20
0
0
0
60
小西 retweeted
A proposal on the Ethereum forum suggests a private stablecoin: pUSD, backed by USDC locked in a smart-contract vault by @_PLabs.
Why it matters: public stablecoins leak data. Once a wallet is linked to a person or business, balances and payment flows are easy to trace.
How it ndable money):
- An operator creates private units that can’t yet circulate or redeem.
- A payment provider deposits 100 USDC, which activates a matching 100-unit private note.
- Both actions happen atomically in one transaction (all-or-nothing).
This means a recipient can receive funds privately from the start—no need to first take public USDC on-chain.
Privacy mechanics rely on zero-knowledge proofs to validate transfers without revealing parties or amounts. Nullifiers prevent double-spends. Redemption is intended to work without the operator’s signature, minus a fee.
Key limits and risks:
- Backing: the vault proves USDC on-chain, not Circle’s off-chain reserves. Circle can still freeze USDC.
- Privacy: mint and redeem amounts stay public; the operator keeps viewing keys for audit.
- Control: a compliance admin can freeze notes; a bad freeze root could halt spending.
- Fiat rails: users still rely on payment providers for bank transfers.
On the composability level, DeFi integration isn’t plug-and-play: pERC20 differs from standard ERC-20. Competing systems (e.g., RAILGUN, Aleo’s USDCx) already offer private stablecoin paths, so PLabs needs to show clear usability and issuance advantages.
Costs are unclear: an older pERC20 benchmark cited ~5.47M gas per transfer (~$263 at 20 gwei, $2,400 ETH), but those numbers may change.
Biggest open question: implementation.
The paper claims fixed verifier keys, but reference code allows admin changes, and there’s no clear evidence of a deployed, independently audited pUSD.
Demand is plausible (payroll, suppliers, treasury), but the case depends on audited contracts, reasonable fees, and transparent viewing-key and freeze policies.
What do you think of pUSD?
Why it matters: public stablecoins leak data. Once a wallet is linked to a person or business, balances and payment flows are easy to trace.
How it ndable money):
- An operator creates private units that can’t yet circulate or redeem.
- A payment provider deposits 100 USDC, which activates a matching 100-unit private note.
- Both actions happen atomically in one transaction (all-or-nothing).
This means a recipient can receive funds privately from the start—no need to first take public USDC on-chain.
Privacy mechanics rely on zero-knowledge proofs to validate transfers without revealing parties or amounts. Nullifiers prevent double-spends. Redemption is intended to work without the operator’s signature, minus a fee.
Key limits and risks:
- Backing: the vault proves USDC on-chain, not Circle’s off-chain reserves. Circle can still freeze USDC.
- Privacy: mint and redeem amounts stay public; the operator keeps viewing keys for audit.
- Control: a compliance admin can freeze notes; a bad freeze root could halt spending.
- Fiat rails: users still rely on payment providers for bank transfers.
On the composability level, DeFi integration isn’t plug-and-play: pERC20 differs from standard ERC-20. Competing systems (e.g., RAILGUN, Aleo’s USDCx) already offer private stablecoin paths, so PLabs needs to show clear usability and issuance advantages.
Costs are unclear: an older pERC20 benchmark cited ~5.47M gas per transfer (~$263 at 20 gwei, $2,400 ETH), but those numbers may change.
Biggest open question: implementation.
The paper claims fixed verifier keys, but reference code allows admin changes, and there’s no clear evidence of a deployed, independently audited pUSD.
Demand is plausible (payroll, suppliers, treasury), but the case depends on audited contracts, reasonable fees, and transparent viewing-key and freeze policies.
What do you think of pUSD?
10
2
22
3,099
小西 retweeted
Arc，补充一下 @mycndota 告诉我的消息：
在Arc Studio构建完应用，去Arc Studio Forum发个帖子分享过程。
Forum→ community.arc.io/home/clubs/arc…
如果你已经是建筑师，在Arc House不能发帖和回复的，可以去下面表格申请权限（秒过）。
表格→ community.arc.io/forms/znonukkj…
在Arc Studio构建完应用，去Arc Studio Forum发个帖子分享过程。
Forum→ community.arc.io/home/clubs/arc…
如果你已经是建筑师，在Arc House不能发帖和回复的，可以去下面表格申请权限（秒过）。
表格→ community.arc.io/forms/znonukkj…
好久没写 @arc 了，更新情报
新出了一个Arc Studio，可以用它在Arc测试网免费做一个简单的应用，能获得200分和Arc Studio徽章
→ 网站 studio.arc.io
→ 使用Arc House邮箱注册
→ 获取测试网USDC
→ 点击Build an app构建应用
全程只需要5分钟
顶级公链啊，值得继续交互，反正也不费时间。
11
5
22
2,569
小西 retweeted
What if we extend the protocol so that anyone can participate in issuing a private stablecoin backed by USDC? @circle @jerallaire @psneville.
Participants would have four potential sources of YIELD:
* Basic yield: the USDC locked in the contract can be deployed to @aave and @Morpho to earn interest.
* Mint/redeem fees: fees from buying and redeeming pUSDC.
* Transaction fees: fees from private pUSDC transfers and trades.
* Token incentives: potential token rewards from the protocol operator.
Beyond yield, the design has major technical ADVANTAGES:
* Permissionless : anyone can participate in issuing the private stablecoin.
* Trustless: funds are held in smart contracts. pUSDC issuers can redeem trustlessly, and pUSDC holders can redeem trustlessly too.
* Always 1:1 pegged: there is no depeg risk. You only have to trust smart contracts and math.
Participants would have four potential sources of YIELD:
* Basic yield: the USDC locked in the contract can be deployed to @aave and @Morpho to earn interest.
* Mint/redeem fees: fees from buying and redeeming pUSDC.
* Transaction fees: fees from private pUSDC transfers and trades.
* Token incentives: potential token rewards from the protocol operator.
Beyond yield, the design has major technical ADVANTAGES:
* Permissionless : anyone can participate in issuing the private stablecoin.
* Trustless: funds are held in smart contracts. pUSDC issuers can redeem trustlessly, and pUSDC holders can redeem trustlessly too.
* Always 1:1 pegged: there is no depeg risk. You only have to trust smart contracts and math.
👀
9
3
24
3,183
小西 retweeted
How we use Zama ?
→ Every NFT mints sealed and is encrypted onchain using Zama’s FHE.
→ The contract computes on data it can never read.
→ Its look and essence are determined by FHE randomness. Nobody gets to choose. Not even us.
🟨 Built with FHE on @zama.
→ Every NFT mints sealed and is encrypted onchain using Zama’s FHE.
→ The contract computes on data it can never read.
→ Its look and essence are determined by FHE randomness. Nobody gets to choose. Not even us.
🟨 Built with FHE on @zama.
4,941
4,947
6,563
180,706
The first private NFT.
The first private token.
PLabs is bringing privacy natively to @Ethereum. x.com/_PLabs/status/…
The first private token.
PLabs is bringing privacy natively to @Ethereum. x.com/_PLabs/status/…
The First Private NFT on @ethereum.
Apply👉: app.plabs.online/privasea/white…
👀 Best takes on Ethereum Privacy → WhiteList.
0
0
0
57
小西 retweeted
The First Private NFT on @ethereum.
Apply👉: app.plabs.online/privasea/white…
👀 Best takes on Ethereum Privacy → WhiteList.
63
68
121
10,364