You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The present transaction envelope specifications are quitebrief. 💭 Namely, there are almost no programmatic examples employing envelopes specifically outside of fee bumps. This despite the reality of envelopes' foundational role throughout the development lifecycle.
What would you like to see?
A page which can be linked as a supplement to the brief glossary index for transaction envelopes. 📄 This full explainer would detail the many creation nuances embedded in managing transaction envelopes across different SDK languages.1 Moreover, it might contextualize the design choices around maximum signers and muxed address storage by explaining how this data gets stored in the transaction envelope object. 🧠
What alternatives are there?
We could leave new developers to uncover these nuances themselves through trial-and-error. However, this would likely lead to underknown bugs in language-specific SDKs, without a common documentation framework to reference. 🐜 Lastly, it'd be a much easier href for citations.
Footnotes
See, e.g., different community interpretations for storing, parsing, and building envelopes. ↩
The text was updated successfully, but these errors were encountered:
What problem does your feature solve?
The present transaction envelope specifications are quite brief. 💭 Namely, there are almost no programmatic examples employing envelopes specifically outside of fee bumps. This despite the reality of envelopes' foundational role throughout the development lifecycle.
What would you like to see?
A page which can be linked as a supplement to the brief glossary index for transaction envelopes. 📄 This full explainer would detail the many creation nuances embedded in managing transaction envelopes across different SDK languages.1 Moreover, it might contextualize the design choices around maximum signers and muxed address storage by explaining how this data gets stored in the transaction envelope object. 🧠
What alternatives are there?
We could leave new developers to uncover these nuances themselves through trial-and-error. However, this would likely lead to underknown bugs in language-specific SDKs, without a common documentation framework to reference. 🐜 Lastly, it'd be a much easier href for citations.
Footnotes
See, e.g., different community interpretations for storing, parsing, and building envelopes. ↩
The text was updated successfully, but these errors were encountered: