卧槽,Fable5.2独立完成模型、声音、贴图全流程,一切皆代码,方法论+源代码全开源!!!
仓库地址:github.com/wquguru/fable52-f…
在线试玩:wquguru.github.io/fable52-fp…
Devon Moon retweeted
我让 Grok 把这个视频里的核心提示词模板搞出来了,方便大家直接抄作业。
完成提示词模板如下:
1、System Prompt(推荐放这里 + 开启Prompt Caching,速度和成本都更优)
你是一位专业的AI助手,帮助瑞典汽车保险公司的理赔员审核瑞典语车祸报告表单。
<form_structure>这是一个标准的瑞典车祸报告表单,分为左右两列:
- 左列:Vehicle A(车辆A)
- 右列:Vehicle B(车辆B)
表单共有约17个复选框行,描述事故发生前的具体情况(如未让行、转弯不当等)。
表单由人工手填,可能使用X、勾、圆圈、涂鸦、文字等各种标记。请合理解读这些标记。
</form_structure>
<guidelines>- 仅基于表单和草图中**可见的信息**进行分析。
- 不要编造任何细节或猜测。
- 如果证据不清晰或不足以做出判断,必须明确说明“你无法以高置信度确定责任方”。
- 保持客观、事实、简洁。
</guidelines>
2、User Prompt(每次输入表单和草图时使用)把两张图片直接上传到Claude(一张是填好的表单 form-numbered.jpg,一张是手绘草图 sketch.jpg),然后贴以下提示词:
[在这里插入表单图片][在这里插入手绘草图]
请分析提供的瑞典车祸报告表单和手绘事故草图,判断哪一方(如果有的话)负主要责任。
严格按照以下步骤执行:
1. 先仔细检查车祸报告表单,逐行列出Vehicle A和Vehicle B所有被标记的复选框(必须列出每个框的具体内容和标记情况)。
2. 再结合表单信息分析手绘草图。
3. 总结事故发生过程。
4. 最后给出责任判定。
<output_format>请将你的最终判定包裹在<final_verdict></final_verdict> XML标签中,便于程序解析。示例:
<final_verdict>Vehicle B 负主要责任。</final_verdict>或
<final_verdict>信息不足,无法以高置信度确定责任方。</final_verdict></output_format>
重要提醒(最终检查):
- 只在有清晰、高置信度证据时才判定责任。
- 否则直接说“无法确定”或“信息不足”。
- 不要添加任何多余的猜测。
3、额外高级技巧(视频最后提到,可进一步优化)
3.1、Pre-fill(预填回复):在Messages API里,把Assistant的第一条消息设为:json,这样Claude会强制从 <final_verdict> 开始输出,解析更干净。
{"role":"assistant","content":"<final_verdict>"}
3.2、Few-shot Examples:如果实际案例里有很多模糊情况,可以在System Prompt里再加3-5个带图片+正确答案的例子。
这个模板就是视频里最终演示的版本,他们现场运行后效果非常稳定,几乎没有幻觉,而且输出格式完美适合后端解析。
Devon Moon retweeted
What we've achieved in the last 13 days since $SORA launch on @BNBCHAIN :
✅ s402.ai live on mainnet
✅ 166+ S402 payments processed
✅ 4600 Followers & die hard community members
✅ Session wallet infrastructure (0-signature payments)
✅s402 Smart Contract
✅The MultiWalletS402Pool uses ten parallel wallets to bypass the single-nonce limit, enabling up to 10x concurrent transactions.
✅ AI Agent Composer with multi-tool orchestration
✅ Full S402 Scan analytics dashboard
✅ v1-v5 of Sora SDK
✅ @BNBChainDevs recognition
✅ BNB Dappbay listing
Must we say more?
Up next (not in order):
- V2 Agent Composer features
- V6 Sora Oracle SDK (Production Ready)
- Premium s402 server partnerships
- Prediction market integration
- 100K queries/day target
- {{Redacted}} 👀
And beyond. We're not here to build vaporware. We're here to prove that agentic oracles powered by the agentic economy work, right here on @BNBCHAIN
🔶🔶🔶🔶
🔶水滴石穿🔶
🔶🔶🔶🔶
Devon Moon retweeted
S402 Scan Architecture 🔶⚡
Built on BNB Chain with:
HTTP 402 micropayment layer
Real-time payment indexer
Claude-powered agent composer
Pay-per-query API marketplace
No subscriptions. Pure usage-based pricing.
Wallet → Payment → API → Response
All settled on-chain.
Devon Moon retweeted
$sora 真的远远被低估 bsc的dev对他们团队很喜欢,我觉得三幻神 poly kalshi opinion还得加一个sora (属于平民的预测市场)
上次space几个要点:
1.团队来自硅谷,目前在台前的人是哥伦比亚大学的,后续他会让其他团队成员也来讲讲话,团队基本都是工程师,技术很强,团队里有华人,一共7-8人
2.有2m美金的私人投资,来自他们的导师和朋友
3.有一个来自迪拜的老外上麦了,说在展会上看到他们的展台了,很惊讶,这么早期的项目竟然有展台,还跟他们团队的人沟通了,所以也不算完全匿名
引用
通过GITHUB
对SoraOracle和OmenOracle的相似度评估
功能:
支持二元(Yes/No)预测市场,通过 oracle 自动结算
价格查询支持(Sora 通过 PancakeSwap TWAP,Omen 通过 BON Oracle 的实时价格
Sora 支持 GENERAL、PRICE、YESNO、NUMERIC;Omen 隐含类似(预测、价格、事件如航班延误)
架构:
两者都是 Solidity 合约集成,但 Sora 是完整的 SDK(包括工具、脚本、测试),而 Omen 更像示例集(接口 + 用例)。Sora 强调无许可 TWAP(时间加权平均价格)防操纵,Omen 聚焦 BON Oracle 接口,可能是一个变体或简化版。
文件生态:
Sora 有全面 README、快速启动指南、MVP 范围(已实现 vs. 未来功能如 AI 自动化);Omen 只提“快速启动”和示例文件夹,缺乏深度
测试和验证:
Sora:测试网 43/43 通过(100% 成功率),主网完整测试(真实 BNB 操作,包括问答和提现)。本地测试套件 21 个测试全通过,覆盖部署、退款、访问控制和边缘案例。零漏洞,gas 节省已链上验证。
Omen:无测试报告、套件或验证提及。只提 BNB 测试网部署,但无证据
安全性能:
Sora:使用 OpenZeppelin v5(防重入攻击、访问控制、输入验证、可暂停)。退款保护(7 天未答退款),紧急暂停。所有功能经审计,无漏洞。
Omen:无提及。示例合约使用 OpenZeppelin(Ownable、ReentrancyGuard),但无全面审计或测试
总结:俩者部署的程度相差很大,但是理念差不多,但是omen的技术可能属于入门
俩者可能选择SoraOracle 用于生产级预测市场,理由是其成熟的 SDK、全面测试,和主网验证。OmenOracle 适合快速原型或独特用例(如航班保险)
核心建设:Deflationary 通过 buyback – 费用 → 回购 $SORA → 减少供应 → 支持价值。
费用:0.01 BNB oracle 费、2% 市场费,大部分用于 buyback。
未来计划:扩展到 SoraMarket,也就是用自己的预言机做一个预测平台,潜在 staking 和 governance(从 MVP 未来功能)
很显然我在space要求项目方团队即便草根团队也需要实名制,但是项目方说目前还不愿意,所以我卖飞了很多筹码,但是对于草根团队和技术方面,我还是觉得我可以留一部分筹码进行观察
对于项目方把自己的预言机基建来建设sora并且所有的费用用来buyback是一个很好的想法
如果后期soramarket能够达到很大的效果或者很大的交易量,这肯定会是一个大金狗,因为很多预言的建设者会尝试交互sora来建设自己的平台,我会持续关注他们的github如果有一些大更新,我会同步进行分析
Let’s talk about x402: the protocol turning HTTP into a native onchain payment layer.
For years, “HTTP 402 Payment Required” sat unused but the x402 protocol changes this.
It turns standard HTTP into a native value protocol, allowing websites and apps to request and settle payments directly onchain.
Here’s what that means:
Instead of the usual “401 Unauthorized” that requires a static API key, a server can now respond with “402 Payment Required” and include an onchain invoice. It’s a simple, stateless, and machine-readable way for digital services to exchange value over the web.
For builders on BNB Chain, this unlocks a new layer of utility:
• Monetize API endpoints directly
• Charge per query, per token, or per compute unit
• Enable autonomous agents to pay each other instantly without pre-set keys
This is where the @BNBCHAIN ecosystem impact begins.
x402 enables a real machine-to-machine economy where agents, data sources, and services interact and pay each other automatically.
Think of an AI agent buying data to complete a task, a DePIN node charging per compute request, or an LLM billing per-token inference, settled in real time.
Each interaction creates thousands of small, automated payments that drive constant blockspace demand and long-term utility for $BNB.
The Core Technical Challenge
The x402 gasless flow relies on EIP-3009 (transferWithAuthorization).
This allows a client (agent) to sign a payment, which a third-party facilitator can then submit, covering the gas.
The problem: major stablecoins on BNB Chain, like USDT, are standard ERC-20s and don’t support this function.
Solution 1: Universal Facilitator Contract (via @AEON_Community)
AEON’s approach introduces a facilitator contract that supports both EIP-3009-enabled tokens and standard ERC-20s.
For standard ERC-20 tokens (pre-step): users authorize the facilitator contract to handle the transaction.
(It’s important to verify the correct contract address and only authorize small token amounts.)
Signature Verification: The AEON Facilitator Contract verifies the signature from the client.
Token Transfer: After successful verification, it interacts with the token contract by calling the standard transferFrom function.
Transaction Execution: The transferFrom function moves the funds — for example, “10U from A to B.”
This works because the client’s wallet pre-approved the AEON Facilitator Contract to spend the tokens.
Solution 2: Asset-Level Wrapper (via @pieverse_io)
Pieverse’s x402b protocol introduces pieUSD, an EIP-3009-compliant wrapper for USDT.
Flow:
• Client → Resource Server: Sends an HTTP request with an X-PAYMENT header that includes the payment and optional compliance metadata.
• Resource Server → Facilitator: Verifies the signature and initiates settlement via /settle.
• Facilitator → Blockchain: Uses the user’s signed authorization to call transferWithAuthorization on the pieUSD contract (gasless).
• Facilitator → BNB Greenfield (optional): Uploads a compliance receipt to Greenfield, creating an immutable and audit-proof record.
• Facilitator → Resource Server → Client: Returns a standard x402 response, optionally including the Greenfield receipt URL.
In simple terms, users sign, facilitators submit, and BNB Greenfield preserves the proof — all within a single, seamless, web-native payment flow.
Solution 3: S402 via MultiWallet Pool with EIP-2612 (the permit function) (via @SoraOracle)
Client-side (User): The user or agent wants to access an API. Instead of signing an EIP-3009 message, they sign an EIP-2612 permit message, authorizing the S402Facilitator contract to spend their tokens.
Backend (Middleware): The S402 service receives this signed permit, verifies the signature to confirm payment intent, but doesn’t wait for onchain settlement.
Backend (API): Once the signature is verified, the API optimistically serves the requested data.
Backend (Settlement): The middleware passes the permit to the MultiWalletS402Pool. One of ten worker wallets (each with its own nonce) submits the transferFrom transaction to the S402Facilitator contract, which pulls the funds and settles the payment onchain, taking its 1% fee.
This setup cleverly works around the EIP-3009 limitation.
The core trade-off: Instead of the unavailable EIP-3009 (transferWithAuthorization), it uses EIP-2612 (permit).
Why this works: EIP-2612 is more common and supported by many ERC-20 tokens on BNB Chain. It also provides a gasless user experience by allowing a signed approval that a relayer can later execute via transferFrom.
The new problem: A single relayer wallet would face a sequential nonce bottleneck.
Sora’s solution: The MultiWalletS402Pool uses ten parallel wallets to bypass the single-nonce limit, enabling up to 10x concurrent transactions.
This design achieves high throughput and reduces cost per payment from about $0.12 to roughly $0.003 by amortizing gas fees.
To make this even simpler, native EIP-3009 enabled assets are in the pipeline.
The autonomous agent economy is being built on the BNB Chain now.
Devon Moon retweeted
V5.0 is dropping on @BNBCHAIN with something we've never seen in prediction markets:
An AI Research Agent that pays for its own data, aggregates multiple sources, and resolves bets automatically with confidence scoring.
This changes everything 🧵👇
Devon Moon retweeted
The countdown begins.
Something big is set to unfold this Thursday.
A foundation is taking shape, one that will anchor the future of on-chain payments.
Stay tuned!
Devon Moon retweeted
提醒一下,最近预测市场很火,但似乎很多人都忽略了它的风险,预测市场在很多地区都被视为赌场(不仅是中国内地、台湾、香港等等),如果你所在法律辖区对此很严格,建议不要参与类似的项目(创业、工作、导流),否则开设赌场罪妥妥等着。同理最近小红书也很多人做 CEX 导流,风险也是非常高。
Devon Moon retweeted
如何规避黑天鹅?很难...
但为何我规避了好几次?
每一次非大熊市期间的黑天鹅爆发之前市场都有异常火热的现象,怎么会那么巧呢?还是并不是巧合?
而大熊市的黑天鹅又为何能规避?
因为“空仓跑赢99%”...
唯一的一次没规避掉是18年底算力战后底部抄底,然后币本位开了多被插针干了...所以我远离了合约
Replying to @TingHu888
❸
比如94
teapawt.org/TingHu888/status/16986…
比如312
teapawt.org/TingHu888/status/14917…
比如519
teapawt.org/TingHu888/status/16556…
比如2022
整年的策略~
黑天鹅确实无法预计,但似乎真的可以无意间规避一些,而这主要得益于什么?运气好!而运气好的背后还有一点就是行情的预判力。
大家不妨找找这些黑天鹅之前的同和不同~
Devon Moon retweeted
今天是注定悲痛的一天。
我给大家聊一聊为什么山寨币会暴跌。也给从业者,交易所,散户一些掏心掏肺的话。
结论放在开头,这次完全是主动做市商的问题,他们无法充分Hedge的典型。这也会写进金融史,给所有金融从业者警醒。
————
首先我们明确,做市商手里的资金是 有限 的,而有限的资金便会对各个项目有区分 有Tier0 Tier1 Tier2 Tier3 Tier4的 给予的流动性供给是不同的。给予Tier0 Tier1项目最多的资金,而其他Tier2 Tier3的项目,则是顺带着做一做。
而在Jump倒台之后,大量的项目流落到主动MM手里,讲白了,就是很野的做市商,他们缺乏充分对冲的意识,对于尾部对冲可能几乎是没有充分思考的,只考虑寻常行情不考虑极端行情。
所以在Trump确定重搞关税的这一刻,资金不够给所有项目托底了。那么只能保证大项目不出问题。原本给小项目托底的资金,甚至会挪用资金给更大的Tier0 Tier1的项目。
这便会导致,当市场出现庞大卖盘/抛压的时候,做市商根本没有足额的资金摆单,这也就导致没有对手盘,价格便一路清算,如iotx一样,直近归零。
那问题来了,为什么之前没有出现类似的问题?
当前的加密市场 主动做市商垫资的部分趋向于饱和,大量的资金压在大项目上,而今年以来Launch的项目过多,早已超负荷,早已无法充分Hedge,市场也缺乏足够多的衍生品进行流动性补充,以对冲。
————
对市场上各类参与者的话
对于Tier1级别交易所来说,需要制定一些风控体系,来防止主动MM出现这类问题,即使风险转移了,但用户是真实受伤的,对交易所声誉依然有相当的负面影响
对于其他需要和用户做对手盘的其他交易所来说,如何有效尾部对冲,将会是一门必修课,而市场上能做好尾部对冲的二级交易员,屈指可数,这并不流通,这也是巨大的挑战。
对于普通散户来说,多次我说过的全仓合约不能碰,需要有足够清醒的认知,需要对安全边际有额外的考量。今天这一天,也会对所有全仓高杠杆用户进行全面的清算,这是一次对于无知的惩罚,这也必将让更多人意识到,什么是流动性,什么是全仓合约,全仓合约的风险到低有多高
对于从业者来说,如果你的产品是一个交易类产品,必须考虑到极端行情,如同今天的行情,你该怎么办?否则来一次你的产品就宣告死亡了,是保用户,还是保交易所,这是一个没有正确答案的两难
对于MM来说,并不是说,你会画线,你会搞200个账号规避风控,你会看oi看费率爆对手盘,你就牛逼,你的风控体系应当是更重要的事情,没有金刚钻就别揽这个瓷器活
甚至有一个暴论,除了目前市场上头部的几家MM,如Wintermute DWF GSR之流,其他的所谓主动MM,将会被清算,只是多和少的问题。
Devon Moon retweeted
再奶一次SOL链的 $CAP 现在市值3.6M
7E2iF4WFs5biCtkAVFCBPEdnpg7t2D19VzxjxEPvpump
板块轮动迟早会来,CAP今天凌晨速通moonshot
要不是现在BSC吸血厉害,这个产品保底都是20M起步..
用户可以通过标记 @capdotbot 在X上快速创建投注,平台会自动生成投注链接。投注过程简化为一键操作,支持对任何话题的预测(如加密货币走势、体育事件、流行文化等)
去年底 @blinkist 开发出了X上一健买币,代币 $blink 最高市值50M
今年初Clout开发出了X上一健发币,后面改名Believe @launchcoin 代币 $launchcoin 最高市值300M
今年10月6日 @capdotbet 开发出了X上一健下注 $cap 最高市值仅仅5M,一个月后 $cap 市值能否到20M?欢迎下注对压!
CAP可以在X上支持“任何事情”投注,拒绝嘴炮,爱杠你就下注!
@toly 确定不转发一下?
Devon Moon retweeted
应该是万亿美金的机会
之前计算保守了
37万亿的美债将增长到50-60万亿
稳定币规模将从2500增长到5-10万亿
一年预计带来1000-2000亿u利息收入
稳定币将会出现2-3万亿美元的总市值
其中crcl将达到25-40%市场份额
预计在5000-1.2万亿美金
这是新的普通人能看得见的抓得住的机会
类似于2027的tsla 和btc
Devon Moon retweeted
I'm seeing quite a bit of comment about this, so I want to make a couple of points.
I'm not owed eternal agreement from any actor who once played a character I created. The idea is as ludicrous as me checking with the boss I had when I was twenty-one for what opinions I should hold these days.
Emma Watson and her co-stars have every right to embrace gender identity ideology. Such beliefs are legally protected, and I wouldn't want to see any of them threatened with loss of work, or violence, or death, because of them.
However, Emma and Dan in particular have both made it clear over the last few years that they think our former professional association gives them a particular right - nay, obligation - to critique me and my views in public. Years after they finished acting in Potter, they continue to assume the role of de facto spokespeople for the world I created.
When you've known people since they were ten years old it's hard to shake a certain protectiveness. Until quite recently, I hadn't managed to throw off the memory of children who needed to be gently coaxed through their dialogue in a big scary film studio. For the past few years, I've repeatedly declined invitations from journalists to comment on Emma specifically, most notably on the Witch Trials of JK Rowling. Ironically, I told the producers that I didn't want her to be hounded as the result of anything I said.
The television presenter in the attached clip highlights Emma's 'all witches' speech, and in truth, that was a turning point for me, but it had a postscript that hurt far more than the speech itself. Emma asked someone to pass on a handwritten note from her to me, which contained the single sentence 'I'm so sorry for what you're going through' (she has my phone number). This was back when the death, rape and torture threats against me were at their peak, at a time when my personal security measures had had to be tightened considerably and I was constantly worried for my family's safety. Emma had just publicly poured more petrol on the flames, yet thought a one line expression of concern from her would reassure me of her fundamental sympathy and kindness.
Like other people who've never experienced adult life uncushioned by wealth and fame, Emma has so little experience of real life she's ignorant of how ignorant she is. She'll never need a homeless shelter. She's never going to be placed on a mixed sex public hospital ward. I'd be astounded if she's been in a high street changing room since childhood. Her 'public bathroom' is single occupancy and comes with a security man standing guard outside the door. Has she had to strip off in a newly mixed-sex changing room at a council-run swimming pool? Is she ever likely to need a state-run rape crisis centre that refuses to guarantee an all-female service? To find herself sharing a prison cell with a male rapist who's identified into the women's prison?
I wasn't a multimillionaire at fourteen. I lived in poverty while writing the book that made Emma famous. I therefore understand from my own life experience what the trashing of women's rights in which Emma has so enthusiastically participated means to women and girls without her privileges.
The greatest irony here is that, had Emma not decided in her most recent interview to declare that she loves and treasures me - a change of tack I suspect she's adopted because she's noticed full-throated condemnation of me is no longer quite as fashionable as it was - I might never have been this honest.
Adults can't expect to cosy up to an activist movement that regularly calls for a friend's assassination, then assert their right to the former friend's love, as though the friend was in fact their mother. Emma is rightly free to disagree with me and indeed to discuss her feelings about me in public - but I have the same right, and I've finally decided to exercise it.
“I think she’s going to find that you can’t sit on the fence... The real win is when ordinary people can say these things.”
@DerryBanShee speaks to @joshxhowie about Emma Watson’s comments about JK Rowling.
📺 youtu.be/r2OGEITYe2Y
Devon Moon retweeted
这个KOL的指标真的是在捡钱,早上的时候我就看到很多人发推看空,看数据也是看空的人多,看未平仓合约也是看空的人更多,我就知道看空的人要芭比Q了
做多的机会来了,上一次KOL做空的时间是9月2号,今天KOL都在做空了。
很好玩的小众平台。
echosync.io/en/tradedata



































