Document Inbox system errors and Privacy Portal recovery flows.#27
Open
naiemk-coti wants to merge 51 commits into
Open
Document Inbox system errors and Privacy Portal recovery flows.#27naiemk-coti wants to merge 51 commits into
naiemk-coti wants to merge 51 commits into
Conversation
- Added a new page for "Manual full node setup (without the web app wizard)" to provide an alternative installation method. - Updated links in the "Features" and "Installation" sections to reflect the new manual setup documentation. - Introduced the "COTI Node Ecosystem Litepaper" to summarize the Node Economy and its incentive rules.
- Reorganized the SUMMARY.md to remove duplicate entries for "Installation" and "UI Guide" under the Node Ecosystem section. - Enhanced the manual full node setup documentation with a note for new users to consider the web app wizard first. - Updated README.md to emphasize the recommended path for new operators and clarify the differences between the web app wizard and manual setup.
- Added a new "Server requirements" page detailing the certified operating system, software stack, and hardware specifications for both the web app wizard and manual full node setup. - Updated the "Installation" and "Manual full node setup" documentation to reference the new server requirements page for clarity on OS and hardware needs. - Improved links and descriptions in the README.md to emphasize the shared requirements across installation paths.
- Changed references from dev.nodes.coti.io to testnet.nodes.coti.io in the manual full node setup and README.md for clarity on the testnet environment. - Removed outdated disclaimers regarding server requirements to streamline the documentation.
- Added new installation guides for "Own domain (Nginx + TLS)" and "Wizard tunnel (COTI subdomain)" to provide clear paths for node setup. - Updated existing documentation to reference the new installation options and clarify prerequisites for each method. - Improved descriptions in the "Installation" and "Features" sections to better guide users through the setup process.
- Adjusted the indentation in SUMMARY.md for better clarity and organization. - Updated links in the "Own domain" and "Wizard tunnel" installation pages to reference the "Manual full node setup" for improved navigation. - Enhanced the "Installation" page to provide a clearer overview of installation methods and their prerequisites.
- Introduced two new images for the FQDN setup process: one for generating a COTI-managed hostname and another for bringing your own FQDN. - Updated the features and installation documentation to clarify the FQDN setup options, including detailed instructions for both generating a hostname and using a custom domain. - Improved descriptions in the UI guide to reflect the new setup steps and enhance user understanding of the installation wizard flow.
- Revised the eligibility rules in backend-services.md, features.md, and glossary.md to clarify the two distinct paths for node reward eligibility: Path 1 (USDC + COTI) and Path 2 (COTI only), emphasizing that uptime is mandatory for both. - Enhanced the eligibility section in the README.md to reflect the updated paths and their requirements. - Updated the eligibility image to visually represent the new criteria and paths for better user understanding.
- Updated the existing dashboard image to better reflect the current UI layout and features. - Added a new image for the Past Epochs table to visually represent historical eligibility data. - Revised the README.md to include detailed descriptions of the dashboard components and their functionalities, improving clarity for users.
- Introduced a new image for the Edit Node flow, illustrating the updated NFT metadata editing process. - Revised backend-services.md and features.md to clarify that the Edit Node flow now allows updates to NFT metadata, including name, image URI, and more-info URL. - Enhanced the README.md to reflect these changes, providing clearer guidance on the Edit Node functionality and its implications for users.
- Revised installation documentation to specify certified operating systems, including Ubuntu 24.04 LTS and Windows 11 with WSL 2 using Ubuntu 26.04 LTS. - Enhanced prerequisites sections across multiple documents to clarify environment requirements for node setup. - Improved README.md to reflect the updated installation flow and supported environments, ensuring clearer guidance for users.
- Changed command line options from `--no-nginx` to `--without-nginx` and `--no-frpc` to `--without-frp` for consistency across the installation guides. - Ensured clarity in the documentation regarding the implications of skipping Nginx and FRPC for users setting up their nodes.
…t setup and clarify init command functionality
…commands for smoke testing
Default coti-private-messaging skill covers setup, grant fallback, and send/read; starter-grant skill is optional troubleshooting only.
…rify private token balance display in MetaMask
…for Nginx and FRPC configurations
…mphasizing default settings and usage flags
…buntu 24.04 LTS compatibility across all platforms
…acOS, and Windows 11, clarifying usage of `sudo` and installer paths
…er usage in URLs for Linux and macOS installers
…ng up Nginx and Let's Encrypt for HTTPS, including prerequisites and troubleshooting steps
…g agent delegation, agent-to-agent messaging, multi-agent coordination patterns, and decision guidelines for using private messaging versus public chat
… agent delegation, agent-to-agent messaging workflows, and production-quality coordination standards
naiemk-coti
force-pushed
the
naiem/updates
branch
from
July 19, 2026 17:29
d6d84c3 to
c894661
Compare
|
|
||
| import "../InboxUserCotiTestnet.sol"; | ||
| import "@coti-io/coti-contracts/contracts/utils/mpc/MpcCore.sol"; | ||
| import "@coti/pod-sdk/contracts/utils/mpc/MpcCore.sol"; |
Member
There was a problem hiding this comment.
[12:06 PM]https://github.com/coti-io/documentation/pull/27/changes <--- privacy-on-demand/tutorial-custom-logic.md line 44 shows the mpccore comes from pod-sdk - but we said that it should not contain it
[12:06 PM]if it gets it as a depedency , still it should not be reffered
…de, API reference, onboarding processes, and example app setup, enhancing developer resources for React/wagmi dApps
…nlock strategies and supported chains, enhancing developer understanding of wallet integration processes
…s on the new "Save Locally" feature, clarifying backup options and UI behavior for Snap and non-Snap wallets
…iling network parameters, contract addresses, and integration roles within the Privacy on Demand ecosystem
…ding architecture, async operations, fee structures, and a detailed cookbook for private investor allocations, enhancing developer resources and user understanding of the PoD ecosystem
Plain-language what/why for the AES key privacy setup.
Explain encode/validateCiphertext failures vs app raise, add glossary terms and portal refund/cancel guidance for SystemFailed flows.
naiemk-coti
force-pushed
the
naiem/updates
branch
from
July 20, 2026 12:08
c894661 to
2c64997
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Document Inbox system errors and Privacy Portal recovery flows.