💱 Classifying the SDEX Holistically
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 48/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
调研方向
Read the linked SDEX and liquidity pools page, especially lines 14–21, alongside the issue’s discussion of offerIDs, contraIDs, and AMMs. Clarify how the SDEX, order book, and liquidity pools relate, and check the claims against the behavior described in the issue. Done means the documentation accurately explains that relationship and the relevant execution terminology.
由索引模型根据 Issue 内容生成。
描述
In the coming months, I will make a bona fide attempt to finish the SDEX page from #338. I want to iron out any of the alignment choices I made drafting those updates beforehand, since by the time I put in the PR, it will be pretty close to some substantive regulatory interactions. Unlike the other guides from that issue, this one will actually be relatively imminently reviewed, and I think it would benefit the network to have many of the clarifications that improve complianceness.
Yes, I decided that is a word, but more importantly than that, these are just factually proper as to the current DEX behavior. The biggest thing in my mind is the current implementation introducing the DEX & liquidity pools. I combine them into a cohesive unit:
Later on, I go to define the placeholder offerIDs generated on execution of market orders and contraIDs, which we have used in our codebase with the Commission's review for at least three years. I'm less worried about the semantics on that, since they make a lot more sense in place. But just for clarity, I want to note it because a native AMM generates a contraID which the user receives in return for marketable execution against an AMM (ref #1545, but I'm not proposing the full implementation here).
Because a user can make an offer which executes against a liquidity pool, it follows that liquidity pools are part of the SDEX. The "SDEX" term itself originates from long before Protocol 18, but nobody ever really bothered to reassess it once AMMs came into Core. If you can start with the order book (via a priced offer) and end on the AMM, then logically those two are part of the same system, even without CAP-37.
- 主要语言
- MDX
- 星标
- 145
- 派生
- 326
- 平均合并
- 2 天 18 小时
- 30 天内合并 PR
- 109
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
stellar/stellar-docs 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 73/100
stellar/stellar-docs#3059 · 2 条评论 ·
维护者通常 1 天内回复
-
raven
难度 1/5 1 小时以内 新手友好度 78/100
stellar/stellar-docs#2998 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
Agent CLI build and deploy guide: captures the contract ID the CLI's own skill says not to可能已有人在做 @kaankacar 于 2 天前认领。 未关闭bot:hands-off
难度 2/5 1-3 小时 新手友好度 65/100
stellar/stellar-docs#2980 · 3 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
bot:needs-decision bot:take js-sdk-v17
难度 2/5 半天 新手友好度 62/100
stellar/stellar-docs#2968 · 4 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
stellar/stellar-docs#2921 · 1 条评论 ·
维护者通常 1 天内回复
查看 stellar/stellar-docs 的全部 Issue
相似的 Issue
-
area:mcp effort:low P5 source:agent
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
README says the land/sea mask must match the XS grid; the demo mask does not, and Step 4 works可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭documentation
难度 2/5 1-3 小时 新手友好度 72/100
buckai-observatory/Automated-Cloud-Removal-and-Seamless-Satellite-Image-Mosaicking-Pipeline#52 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 82/100
run-llama/llama_index#24163 ·
维护者通常 1 天内回复
-
documentation good first issue severity: low
难度 2/5 1-3 小时 新手友好度 83/100
TMHSDigital/Static_Chess#48 ·