-
Notifications
You must be signed in to change notification settings - Fork 231
📝 Refresh six classic guides #723
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
Hi @JFWooten4! The bounty is over but we'll still accept and award this PR whenever it's ready!! Thanks for all your work on this one! |
|
Understood @briwylde08—appreciate your support. 🫱🏼🫲🏻 I'd also like to thank @silence48, @earrietadev, @ducksquaddd, and @conveyGhost for their helpful perspectives around native protocol AMMs. Further shoutout to @orbitlens who was a vocal early advocate of developing the most efficient system. |
We're walking through an example implementation for general understanding, but the efficient implementation here likely falls on the applicator.
I just don't see why we need to explicitly walk through this in a relatively advanced guide.
Not convinced we need to include txn submission for the third time.
The higher fee assumes we want these executed in the same block, so let's bid for that. Also, since this is an advanced guide, I'm taking out the redundant/verbose tx timeouts.
silence48
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple issues on the js example.
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
docs/learn/encyclopedia/transactions-specialized/channel-accounts.mdx
Outdated
Show resolved
Hide resolved
I've finally hit my breaking point and am upgrading to Ubuntu. Accordingly, I'm synching up my last local changes despite the reality that I've held these back for some time because most of the substance was moved to protocol discussion 1558. But thanks, reccomendation, and shoutout to Silence for dropping in with some stellar wisdom. 🤝🧙♂️🧠
|
Hi @silence48, thank you for the thoughtful review of that last js example draft! It's been an inspiring week per some stellar feedback from regulators and community developments. Working on those likely till Sunday, and I'll be back to respond to the specifics early next week. 🤝📅 As I'm writing this, I see someone out my window mowing yards on a riding lawn mower which must cost at least $5,000. Indeed, this professional works only to mow lawns and offer other such yardwork in the area. It's this longstanding specialization that enables exponential social progress, progress which can too easily be halted by monopolization. It's in this context that I ask if we might further advocate for specialized open-source work? Namely, it's our understanding that true sustainability for community members like yourself to just do stellar work and receive fair compensation. It's in this context that I'd appreciate the opportunity to share some thoughts on decentralizing our documentation, the very tool which widely introduced me to Stellar in the first place.1 1. Initial ReactionsYour brief review points bring up some material background which seems relevant in the context of this PR and other discussions or issues previously referencing it. Accordingly, might I share my overarching thoughts about the specific items you brought up? 💬 Namely, I am not and do not consider myself to be a coder. All of the production applications I've written are in Python, which is why I mapped out the basic premise like that first. After that, I'm onto ChatGPT and such to preliminarily translate the info as requested. 👩💻 I think there are some challenges on that side because it doesn't seem to understand how Go account address resolution works—something I understand you've actually trained a model around for more accurate results in all languages. Like other community members, I am much more of a writer and strategist, outside of my true call in asset management. And I believe these educational skillsets are crucial to widespread adoption of the network. Given the sunsetting of SCF education grants by my present understanding, might I share some more thoughts on the documentation, governance, and progress of Stellar? 🌌 2. An Abundant Network OpportunityI think you more than anyone have seen firsthand just how creative our community can be given adequate resources. Particularly, it's my understanding that many projects solicit your consultation because of your active, generous, and timely support on Discord. 💜 The incredible reality of this work is that it enables specialization, a tool so crucial to efficient capitalist society.2 2.1 Fostering DirectnessIndeed, most of the challenges in this particular example come from an unfinished draft incorporating the AI response into the page. However, I ran out of time that night, and just 'saved' my progress with an incomplete commit, per the added line spacing separation. 💾 In fact, I was quite struggling with the inheritance part, as that's something I've always had a tough time with in JavaScript. I think we build better when everyone can learn, reference, and iterate on prior research. There doesn't seem to be any reason in my mind that composability ought disappear when we enter the realm of decision making, as is so often the case in mammoth policy releases from a select few middlemen. If we agree that anyone anywhere ought to be able to develop their problem-solving skills, might we develop a collective strategy to make our choices more open to public review? 👁️ Namely, it can be challenging to comprehend the operations of some stellar production applications based on their source code alone. Indeed, I intrinsically believe that the only way to end "back-room deals" is for all stakeholders to apply the "cleansing sunlight of transparency" praised by President Barack Obama. And in the sense of open source free communities, well, that happens to be all of humanity. 🌍 2.2 Efficiency for the ImpoverishedLow net worth is a temporary status, and I'm obsessed with how we might empower masses of people to change that state via Stellar.3 A couple days ago, I was looking to schedule some flights back home/to family for holidays—Thanksgiving in particular. I needed to confirm some times with my partner and such, so I waited till this morning to buy the tickets since she was at work. But when I went back to secure my flight yesterday, the price for one leg increased by 80% just this morning. Comparatively, aviation used to be regulated down to a specific cost per mile, so as to promote equal access opportunities.4 Without an efficient American rail system, I'll indeed be at the whims of the oligopolies of how much of my rent savings go towards this particular trip, albeit at my fault partially for not confirming some family event dates earlier. Thankfully, our diverse, brilliant, and hardworking community seems to fall on the more considerate side of this scale. 🫱🏿🫲🏻 Indeed, it's the dramatic efficiency baked into native operations which so effortlessly empower the masses to employ the financial system, not the other way around via a select few middlemen.5 I find this particularly inspirational given the precedent of blockchain rent-extractors copying major innovations for the sake of short-term profits at the expense of long-term sustainability. 2.3 Shared, Nonproprietary Market UpgradesI wholeheartedly believe that only together do we stand a chance at freeing our markets from Wall Street's tight oligopolistic grasp. And if we elect to act in unison, it seems like we might just give investors the saving grace they didn't know they needed. Might we act collectively amidst this great turning point so that the next great financial system doesn't face the quandaries of today's? Indeed, if we are all sincerely "driven by technology that helps people to truly own what is theirs," then it seems natural that the network's documentation itself ought live at the whim of the community. Do you find this perspective particularly material, given:
3. Ownership for AllAs inspired by our community and deeply evident in the Network's design, might we continue advocating for the foundational promise of usable self-custody? It's my view that this mission starts at the core of our open-source advocacy, advancements, and accessibility. Namely, it's only when changes are clicks away that the dispersed, impoverished, and developing citizens spread across this vast world might coherently collaborate towards our grander mission. 🚀 Do you think it's possible and worthwhile to engineer these free markets? Might the crowdsourcing ethos so evident in protocol development itself spread to the key responsibility of widespread education through the docs themselves? 📖 This is what I think of when contemplating your generous, unsolicited, and pertinent feedback, Silence. We're tackling an unprecedented common enemy with a unique ability to buy their way out of every past catastrophe. As someone that didn't attend Meridian due to cost, I believe so wholeheartedly that the unique community consensus methods employed by Stellar can sincerely replace their broker monopolies. Might we contemplate further how employing a regulation-aware development strategy could best serve us? Might we venture on the path less traveled? 🛤️ Footnotes
|
file header diction relies on bhasis on /build/guides `Contract Testing` sectn
for additional pathPaymnet info box, see https://github.com/script3/auctioneer-bot/blob/b75f3e874a9eeb2acf71049a28ce8fd3cb4289be/README.md?plain=1#L117 another 20% into PP should get it sturdy
re stellar#1529, there is too much here based on the pathfinding and result data to change trade ex.s for this PR communicated to Bri at 12:21pm ET, 22 sep 25
see stellar#723 (comment) has only application i n ID ownership keeps paths to horizon/payments pg
stellar#1819 needs to directly change the header sidebars with weights
*does not contemplate mobile*
Bringing the material `object` relevance into src in deferencce to stellar#1778
Migrating immediate material changes from stellar#1670 (comment).
|
Might want to translate the related examples for data calls in the migration RPC. |
JS translate 1/2 for "DocCard/index" perfects stellar#2116
implements stellar#1828 translated into mermaid

Solving #338 🤝