<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Scopuly on Medium]]></title>
        <description><![CDATA[Stories by Scopuly on Medium]]></description>
        <link>https://medium.com/@scopuly?source=rss-bdf7585e89c7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*-oHcSslPu90l-W8xM-2-kg.png</url>
            <title>Stories by Scopuly on Medium</title>
            <link>https://medium.com/@scopuly?source=rss-bdf7585e89c7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:11:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@scopuly/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Your Stellar address stays yours: inside Scopuly’s new wallet protection]]></title>
            <link>https://scopuly.medium.com/your-stellar-address-stays-yours-inside-scopulys-new-wallet-protection-2718c89d7cf7?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/2718c89d7cf7</guid>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 18:43:45 GMT</pubDate>
            <atom:updated>2026-11-15T18:44:22.317Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NgDBVPDh2VhbDs7J3QXk9g.png" /><figcaption>Scopuly encrypts saved keys on your device. Your Stellar address and balance stay the same.</figcaption></figure><p>If you’ve used the same Stellar wallet for years, the first question a security update raises is a practical one. Will you need to find your recovery phrase, move your balance, or ask people to start paying a new address?</p><p><strong>If your wallet is already saved in Scopuly on this device, you can update its protection without doing any of those things.</strong> The update happens locally. It costs no fee and requires no Stellar transaction.</p><p>Scopuly now keeps saved wallet keys in an encrypted vault across mobile, desktop and web. Think of the address your customers use to pay you in USDC. Its balance, trustlines, signers and transaction history belong to the account on Stellar. Your device holds a key that can authorize transactions for that account. This release changes how Scopuly keeps that key between sessions. A customer can continue paying the same address throughout the upgrade. <a href="https://developers.stellar.org/docs/learn/fundamentals/stellar-data-structures/accounts">How accounts work on Stellar</a></p><h3>Already using Scopuly? Start with the device you have</h3><p>There are two different situations. If the wallet is still saved in an installation you can open, use <strong>Update wallet protection</strong> there. If you have a new phone, reinstalled the app, or cleared its data, use <strong>Connect Wallet</strong> to restore from a backup. Only the second situation calls for recovery material.</p><h3>Update the wallets already saved here</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VXcoQGDpE332nm-EQK7Czw.png" /><figcaption>Update protection on the device that holds your wallets. No recovery phrase or network fee is required.</figcaption></figure><p>Open your usual Scopuly installation. On the web, use the browser profile where the wallets are saved and close any tabs still running the older release before upgrading. Keep the app and its data in place.</p><p>On <strong>Update wallet protection</strong>, choose <strong>Update protection</strong> and follow the unlock setup offered on your device. If you choose a local password, enter it twice. Depending on your previous security settings, Scopuly may also ask for your existing Scopuly PIN or device confirmation. You can open <strong>Learn more</strong> on this screen before deciding.</p><p>Here is what happens when you confirm. For each saved record containing a secret key, Scopuly derives its Stellar public address and checks it against the address already stored. It then encrypts the wallet records and writes a candidate copy. It reads that copy <strong>back from storage</strong>, decrypts it and compares the result with the records being migrated. It also checks that the original wallet entry hasn’t changed in the meantime. Only then does it replace the original entry.</p><p>That order matters. If the device cannot write or verify the new copy, the old entry has not been replaced. If an update is interrupted, reopen the updated app with its data intact. Clearing storage would remove the local copy you are trying to protect.</p><p>If the screen offers <strong>Skip for now</strong>, you can finish later in <strong>Settings → Wallet protection</strong>. Until then, the existing wallets keep their previous storage format. Finish the upgrade before saving another wallet. If you use Scopuly on a second device, its local copy has its own protection setup.</p><h3>Reconnect an older wallet on a new device</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QH1D-fomP6w08RDgyKyuEQ.png" /><figcaption>Restore with your 24 words, original Stellar address, and any passphrase used at creation.</figcaption></figure><p>Open <strong>Connect Wallet</strong>. If the old device still works, keep it available until you have confirmed that the new installation opens the expected address. The right connection method depends on what you saved when you created the wallet.</p><p><strong>You have 24 recovery words and used a password when creating the wallet in an older version of Scopuly.</strong> Select <strong>Pass Phrase</strong>. Enter the words in their original order, your original public address, and the password used at creation in <strong>Original wallet password (if used)</strong>. Then select <strong>Login with Phrase</strong>.</p><p>That original password had a specific purpose: it was an input to the derivation of your signing key. The same 24 words combined with a different passphrase can produce a different, valid keypair. Your known public address gives Scopuly a way to tell whether it recovered <em>your</em> account. If the address check fails, check the words, their order, the address and that original password.</p><p><strong>You have 24 words and never used an extra creation password.</strong> Enter the words and original public address, and leave <strong>Original wallet password (if used)</strong> empty. This also applies to wallets created with the new flow. The local password chosen on the first device belongs to its vault. Putting it in the recovery-passphrase field would change the derivation.</p><p><strong>You have the Stellar secret key.</strong> Choose <strong>Secret Key</strong>, enter the full key and select <strong>Login with Secret Key</strong>. The backup already contains the signing key, so Scopuly can derive the public address directly. This route works without the original words or creation password. Anyone who obtains the secret can use it independently of your device, so enter it only in your own trusted installation.</p><p><strong>You have only the public address or an old Scopuly PIN.</strong> An address lets you identify and follow an account. A PIN can confirm actions inside an installation you control. Neither can reconstruct the signing key. Preserve any device that still opens the wallet and check your backups before disconnecting it.</p><p>After a successful restore, Scopuly asks you to protect the first signing wallet before saving it on the new device. You can choose a <strong>new local password</strong> here. If this installation already has an unlocked vault, the imported key joins it.</p><p>We tested this distinction with an older password-derived account. With the original words but no original passphrase, the address check failed and no wallet was saved. With the original passphrase, Scopuly recovered the expected public address. We then chose a different password for the new local vault and opened that same account.</p><h3>Creating a new wallet: what to save, and why</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*58qSLVDYfDMA7uN5RuujAQ.png" /><figcaption>Verify your 24 recovery words, then save the public address with your backup.</figcaption></figure><p>Choose <strong>Create Account</strong>. In the password flow, <strong>Set Password</strong> asks you to enter and repeat a local password. The minimum is eight characters. Choose a long, unique password because it protects the signing keys saved together in this installation. You can also give the wallet a recognizable name. On supported mobile devices, Scopuly can use device unlock. When you create another wallet in an already unlocked vault, it uses the existing local protection.</p><p>Scopuly generates <strong>24 recovery words</strong>. Save them privately in the exact order shown. <strong>Copy Phrase</strong> and <strong>I saved this phrase</strong> lead to <strong>Check Phrase</strong>, where you enter the words again. The check gives you a chance to catch a missing or misplaced word while setup is still open. Make sure you have a durable backup; the clipboard is only an intermediate step.</p><p>After the phrase check, review the backup acknowledgements and choose <strong>Confirm</strong>. On <strong>Wallet Created!</strong>, <strong>Copy Public</strong> and <strong>Copy Secret</strong> serve different purposes. Keep the public address with your recovery record so you can verify the account later. Protect the secret key as a complete alternative backup with signing authority. After saving both, select <strong>Open wallet</strong>. Scopuly saves the key through the encrypted vault.</p><p>Each additional wallet has its own signing key and recovery material. One local unlock can open several wallets, but backing up the first wallet’s phrase does not back up the others.</p><h3>What protects the keys between sessions?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VqiwZ-CR0ePfhLN_FIw3Zg.png" /><figcaption>One local unlock opens the wallets in Scopuly’s encrypted vault.</figcaption></figure><p>Imagine someone obtains a copy of a locked app profile. A screen lock can prevent them from tapping through the app, but that alone does little for a file they already possess. Scopuly encrypts the wallet records themselves. Opening that copy requires the vault key or the ability to reproduce it. In password mode, someone holding the encrypted data can try guesses offline. This is why password quality still matters.</p><p>Scopuly uses TweetNaCl’s <strong>XSalsa20-Poly1305</strong> secretbox with a 256-bit key and a fresh random 24-byte nonce for each write. Authenticated encryption both conceals the contents and checks their integrity when opened. A wrong key or modified ciphertext fails verification. <a href="https://doc.libsodium.org/secret-key_cryptography/secretbox">Authenticated encryption and secretbox</a></p><p>The same vault format supports several unlock methods:</p><ul><li><strong>Local password.</strong> Scopuly derives a 256-bit key with PBKDF2 using SHA-256, 600,000 iterations and a random 32-byte salt at setup. The work factor raises the cost of each password guess. Separate salts cause two installations using the same password to derive different vault keys.</li><li><strong>Device unlock on supported iOS and Android devices.</strong> Scopuly generates a random 32-byte secret and registers it with the native protected-secret plugin. During setup it reads the secret back and verifies it. On subsequent unlocks, the operating system handles user verification before the plugin releases the secret.</li><li><strong>Passkey on supported web and desktop configurations.</strong> Scopuly requests user verification and uses the WebAuthn pseudorandom-function extension (PRF) to obtain 32 bytes of vault key material. A successful identity prompt alone is insufficient: the authenticator must deliver the PRF result. The available method depends on the device, runtime and authenticator. <a href="https://www.w3.org/TR/webauthn-3/#prf-extension">WebAuthn PRF extension</a></li></ul><p>For Stellar developers, the distinction is visible in the key paths. Scopuly’s phrase recovery derives an Ed25519 signing key using the hardened path m/44&#39;/148&#39;/account&#39;. Separately, the local unlock method supplies the vault key that encrypts the saved wallet records. Changing the unlock method therefore requires re-encrypting the local records. It does not require changing the Stellar account’s address, signers or thresholds.</p><h3>Everyday use: unlock, step away, approve a payment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RxfYBILD0DyLd8o0yzREvw.png" /><figcaption>Set an auto-lock timer for inactivity and an optional PIN for transactions.</figcaption></figure><p>When you open a fresh session, <strong>Unlock your wallets</strong> uses the method configured for that installation. A device-protected mobile vault can open the system prompt automatically. In <strong>Settings → Wallet protection</strong>, <strong>Wallet unlock</strong> shows your current method. To switch to a supported alternative, first confirm your current method. Scopuly verifies the newly encrypted copy before replacing the previous one.</p><p><strong>Auto-lock</strong> is off by default for a new setup. You can choose 5, 15 or 30 minutes, 1 hour, or 1 day. A previous 30-minute lock preference carries through the upgrade. Time spent in the background counts. For example, if you choose five minutes and leave the app to answer a call, you’ll need to unlock again if that interval has elapsed.</p><p>On the web, tabs can stay open and unlock independently. A supported refresh in the same tab can resume an unlocked session through a single-use, 15-second handoff held in memory. Only a random ticket enters session storage, and the inactivity deadline carries over. A new tab or a missed handoff requires unlocking again. In native installations that enforce one active session, <strong>Scopuly is open elsewhere</strong> tells you to close the other app window so access can resume.</p><p><strong>PIN for transactions</strong> is a separate choice. Unlocking gives the session access to your saved wallets. Enabling the optional PIN adds a confirmation for transactions and dApp signing requests. The four-digit PIN has its own salted verifier and is never used as the vault encryption key. Verified Mainnet x402 payments also require fresh approval for each payment.</p><h3>If you forget the local password</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-uieWAuS6vbJ1wDWtKmRTg.png" /><figcaption>Check each wallet’s backup before disconnecting. Scopuly removes the keys saved in this installation.</figcaption></figure><p>Select <strong>Forgot password?</strong> to read the recovery options. In a device-protected vault, the entry may say <strong>Can’t unlock?</strong>. Opening <strong>Disconnect all wallets?</strong> does not remove anything. <strong>Back to unlock</strong> takes you back.</p><p>To disconnect, you must type <strong>DISCONNECT</strong> and confirm. That action removes the locally saved keys from this installation. The accounts remain on Stellar, but you still need a valid backup or another working signer to use them. <strong>Check the backup for every wallet before confirming.</strong> If another installation still opens your wallets, verify the addresses and backups there first. A local reset cannot reveal a forgotten password or reconstruct a missing secret.</p><h3>Why this matters for Stellar users</h3><p>One address may receive years of customer payments. Another may be a signer on an account shared with colleagues. A third may be an issuer address you only watch. Scopuly lets you protect the keys you hold together, keep watching addresses for which you hold no key, and change how you unlock a device without asking customers to update a payment address or partners to replace a signer.</p><p>The vault protects stored data. Once unlocked, the app needs access to signing material for operations you approve. Encryption cannot reverse an authorized payment, protect a secret that someone copied before the upgrade, or make a compromised operating system trustworthy. Recovery backups, the inactivity setting and payment approval each address a different part of that problem.</p><p>What this release gives a long-time wallet owner is continuity. Your phone can change. Your unlock method can change. With the right backup, the Stellar address that people know and use can stay yours.</p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2718c89d7cf7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scopuly Is Integrating WalletConnect Pay for USDC Payments on Stellar]]></title>
            <link>https://scopuly.medium.com/scopuly-is-integrating-walletconnect-pay-for-usdc-payments-on-stellar-053042941dfa?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/053042941dfa</guid>
            <category><![CDATA[scopuly]]></category>
            <category><![CDATA[usdc]]></category>
            <category><![CDATA[walletconnect]]></category>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[payments]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 00:20:31 GMT</pubDate>
            <atom:updated>2026-11-15T00:20:31.539Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NCOCT96ITUt8kSsc6og9AQ.png" /><figcaption>Scan a merchant’s QR code or paste a payment link, then choose the Stellar account you want to use.</figcaption></figure><p><em>With merchant payments taking shape in Bermuda, here’s a first look at how you’ll be able to review and pay a merchant’s bill from your Scopuly wallet.</em></p><p>Our first live test started with a one-dollar bill. We entered <strong>$1</strong> in WalletConnect’s point-of-sale app, opened the QR code in Scopuly, and selected a Stellar account. Scopuly displayed the merchant’s name and <strong>1 USDC</strong> for approval. We stopped there to verify where the funds would go before signing.</p><p>That test is part of our work to bring <strong>WalletConnect Pay</strong> to Scopuly. Once the integration launches, you’ll be able to use the USDC in your Stellar wallet to pay participating merchants. One of the first places this could come in handy is Bermuda, where a local ticketing platform is preparing to offer digital asset payments.</p><h3>Why Bermuda?</h3><p>In October 2026, WalletConnect announced expanded support for Stellar and a partnership with Penrose Partners to bring WalletConnect Pay to merchants in Bermuda. The first merchant named was <strong>Premier Tickets (PTIX)</strong>, a platform that sells tickets on behalf of independent event organizers. PTIX payments are expected to go live in <strong>Q2 2027</strong>. Scopuly will announce its own release date separately. <a href="https://stellar.org/press/walletconnect-expands-stellar-network-support-and-partnership-with-penrose-partners-to-bring-walletconnect-pay-to-bermuda-in-support-of-the-government-s-onchain-economy-vision">Read the announcement on Stellar.org</a></p><p>Ticketing illustrates why this matters. You might buy tickets to two events on the same website, even though a different organizer runs each one. Under the model announced for PTIX, each organizer will receive the proceeds for its own event without the ticketing platform taking custody of the funds. For the buyer, the experience will start with a familiar choice at checkout: how would you like to pay?</p><h3>From the merchant’s QR code to your wallet</h3><p>Imagine you’ve chosen your tickets and a QR code appears on your laptop. You’ll be able to scan it with Scopuly on your phone and choose the Stellar account you want to pay from. The wallet displays that account’s available USDC balance, so you can see whether it covers the purchase.</p><p>If you’re using Scopuly on the same computer as the checkout, a screenshot works too. You can paste the QR image from your clipboard, open a saved image, or paste a payment link directly. Each method opens the merchant’s request for review.</p><p>Some payments require additional information. When that applies, WalletConnect presents its personal details form before you review the transaction.</p><h3>What you’ll see before signing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*as-x8Sm7Ipbjmplg7rJHGQ.png" /><figcaption>A demo request from Bermuda Café for 1.25 USDC, ready to review in Scopuly.</figcaption></figure><p>In the example shown here, <strong>Bermuda Café</strong> is requesting <strong>1.25 USDC</strong>. On the <strong>Review payment</strong> screen, you can check the merchant, the exact amount, the account you’re paying from, and the receiving address in the Stellar transaction. Both addresses are shortened to fit the phone screen, and you can copy either one in full.</p><p>WalletConnect covers the Stellar network fee for this payment. If you have enough USDC for the purchase, you won’t need to top up XLM just to cover that fee.</p><p>A countdown shows how long the approval remains valid. If it expires while you’re checking the details, you can refresh the request and review it again. Opening the QR code gives you time to make that decision. You authorize the payment when you choose <strong>Confirm payment</strong>.</p><h3>What happens if the connection drops?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BFkuJsFNk00DCPekkObkWQ.png" /><figcaption>While the demo payment is processing, you can check its status from the wallet.</figcaption></figure><p>One of the more awkward moments at checkout is losing your connection just after you confirm. You want to know whether the payment went through before you try again.</p><p>In Scopuly, you can return to the original request in <strong>Recent payments</strong>. If the result is still pending, <strong>Check status</strong> looks up that payment without sending another one. Once WalletConnect reports completion, Scopuly shows the merchant, amount, and a payment ID you can copy for support. When a transaction link is available, you can also open the Stellar transaction to inspect its on-chain details.</p><h3>Where the integration stands</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lp8rKaJCCI7w0_s8scFNrg.png" /><figcaption>The completion screen for the simulated Bermuda Café payment, with its payment ID and transaction link.</figcaption></figure><p>The Bermuda Café screens use demonstration data from the current Scopuly interface. In our separate live POS test, we verified the path from a merchant’s QR code to the correct USDC amount on the approval screen. In our live POS test, Scopuly opened a merchant’s QR code and displayed the requested 1 USDC for approval. We’re now testing the full checkout experience ahead of release.</p><p>After end-to-end testing and WalletConnect’s review, we’ll share Scopuly’s launch date and a walkthrough of a verified purchase, from the QR code at checkout to confirmation that the merchant received the funds.</p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=053042941dfa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scopuly - Stellar Signer 0.3.8: A Clearer Connection to Stellar dApps]]></title>
            <link>https://scopuly.medium.com/scopuly-stellar-signer-0-3-8-a-clearer-connection-to-stellar-dapps-0a2ce06d5edc?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a2ce06d5edc</guid>
            <category><![CDATA[browser-extension]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[scopuly]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 07:59:41 GMT</pubDate>
            <atom:updated>2026-10-30T07:59:41.407Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wXJBYoU-Q3WX4bxc6OsC8A.png" /><figcaption>Scopuly Stellar Signer 0.3.8 brings clearer account controls and dApp connections to Chrome, Edge, and Firefox.</figcaption></figure><p><em>A refreshed interface, clearer account controls, and request activity - available for Chrome, Edge, and Firefox.</em></p><p>Scopuly - Stellar Signer 0.3.8 is now available in the Chrome Web Store, Microsoft Edge Add-ons, and Firefox Add-ons.</p><p>This release improves the connection between Stellar applications in your browser and your paired Scopuly wallet. Your account takes center stage, connected websites are easier to manage, and recent activity gives you a clearer view of request status.</p><p>Throughout the experience, one principle stays the same: <strong>sensitive requests are reviewed and approved in your paired Scopuly app.</strong></p><h3>Your Account, Front and Center</h3><p>The updated home screen places your shortened public address at the center of the interface, with direct actions to copy it or open it in the explorer. Account selection and network controls sit nearby.</p><p>Rounded cards give the wallet, connected websites, and request activity a consistent visual style across light and dark themes.</p><p>Connected dApps appear below your account. From there, you can inspect the account shared with a website, review its permissions, open the full connection list, or disconnect sites you no longer use. The full settings page remains available for security and appearance preferences.</p><h3>A Clear Account for Each Website</h3><p>You may use different Stellar accounts for different applications. Scopuly lets you choose which paired public account each website can access.</p><p>Those connections retain their account assignments when you change the default account for new connections. This helps keep an existing dApp connected to the account you originally selected.</p><p>Version 0.3.8 also improves device-specific account handling, including situations where the same Stellar address is paired through more than one signing session.</p><h3>Approval Stays in Scopuly</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W9JQGNI-KiwUgvaHWKRV0w.png" /><figcaption>Sensitive requests are reviewed in your paired Scopuly app, while secret keys stay out of the browser extension.</figcaption></figure><p>The extension connects a browser dApp to a compatible Scopuly app on your signing device. <strong>Secret keys and seed phrases never enter the browser extension.</strong></p><p>Sensitive requests require review and approval in the paired app. The extension does not create or recover wallets.</p><p>Supported operations include:</p><ul><li>Stellar transaction signing</li><li>SEP-53 message signing</li><li>Soroban authorization signing</li></ul><p>Returned signing results are independently verified by the extension before they are delivered to the requesting application. Both <strong>Stellar Mainnet and Testnet</strong> are supported.</p><h3>Recent Activity with Useful Context</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HtVpwY8baAb9pz1vLqJ1wQ.png" /><figcaption>Review request details, configure website protection, and manage local activity records through Scopuly’s security controls.</figcaption></figure><p>The activity view brings recent request statuses, website details, and timestamps into compact cards.</p><p>You can distinguish completed requests from rejected or cancelled ones and see which website initiated each request. Activity remains accessible without taking priority over your account and connected dApps on the home screen.</p><p>This history records request statuses locally in your browser. For on-chain transaction details, use the explorer.</p><h3>A Dedicated x402 Integration Path</h3><p>For developers, version 0.3.8 introduces the dedicated signX402Payment provider method.</p><p>It carries the original payment challenge and the protected resource URL alongside the authorization entry. This gives the signing flow the context needed to check payment terms independently.</p><p>The method requires a compatible updated signer and relay. Unsupported signers reject the request without falling back to generic signing.</p><p>Developers should confirm compatibility with the paired wallet build before integrating the complete payment flow.</p><h3>Get Started</h3><p>Install or update Scopuly - Stellar Signer from your browser’s store:</p><ul><li><a href="https://chromewebstore.google.com/detail/gfblddiiepicpjpffokeojikcphggmmd"><strong>Chrome Web Store</strong></a></li><li><a href="https://microsoftedge.microsoft.com/addons/detail/dgdmamodkdcafjehfelpcnifpldbfmai"><strong>Microsoft Edge Add-ons</strong></a></li><li><a href="https://addons.mozilla.org/en-US/firefox/addon/scopuly-stellar-signer/"><strong>Firefox Add-ons</strong></a></li></ul><p>Pair a compatible Scopuly app, choose the public account you want to share with a dApp, and review the website and request details before approving in Scopuly. A compatible signing app and an internet connection are required.</p><p>For product details and developer integration information, visit <a href="https://extension.scopuly.com/"><strong>extension.scopuly.com</strong></a>.</p><p><strong>Connect. Review. Approve in Scopuly.</strong></p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a2ce06d5edc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From AI Prompt to Stellar dApp: Scopuly Joins Stellar Skills]]></title>
            <link>https://scopuly.medium.com/from-ai-prompt-to-stellar-dapp-scopuly-joins-stellar-skills-52806675c984?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/52806675c984</guid>
            <category><![CDATA[ai-coding]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[scopuly]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 09:47:37 GMT</pubDate>
            <atom:updated>2026-10-07T09:47:37.292Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PsGFNMh3jQdIjD01cCjotA.png" /><figcaption>From AI Prompt to Stellar dApp - Scopuly Joins Stellar Skills</figcaption></figure><p><em>Give your AI coding agent the context to integrate Scopuly - with practical examples, explicit wallet approval, and fewer API guesses.</em></p><p>“Add wallet connection to my app.”</p><p>It sounds like a simple request for an AI coding agent. But a working wallet integration involves much more than rendering a button.</p><p>The application needs to detect the wallet, request account access, understand the selected network, handle rejected requests, and distinguish a signed transaction from a confirmed payment.</p><p>Without the right context, an agent can produce code that looks convincing while using the wrong method, expecting the wrong response format, or overlooking an account change during signing.</p><p>We built <strong>Scopuly Wallet skill</strong> to give developers and their AI agents a concrete reference for these details. It is now listed in the <strong>Community skills section of </strong><a href="https://skills.stellar.org/"><strong>Stellar Skills</strong></a>.</p><p>Here is what it provides - and how to use it in a real development workflow.</p><h3>What Is Scopuly Wallet Skill?</h3><p>An agent skill is a package of instructions, references, and supporting examples that a compatible AI coding agent can consult while working on a task.</p><p>Think of it as integration documentation organized for use during development.</p><p>The Scopuly skill covers the Provider API and Stellar Wallets Kit integration paths. It includes guidance for connection state, transaction signing, message verification, Soroban authorization, and handling account or network changes.</p><p>Its instructions also establish boundaries: preserve the application’s existing wallet architecture, request approval through the wallet, and never ask for a secret key or seed phrase.</p><p>You can inspect the complete package in the open-source <a href="https://github.com/Scopuly/scopuly-skills">Scopuly Skills repository</a>.</p><h3>Why the Stellar Skills Listing Matters</h3><p>Developers can now discover the Scopuly skill while exploring tools for AI-assisted development on Stellar.</p><p>The listing connects the Stellar Skills catalog to our independently maintained repository. Our contribution was incorporated through <a href="https://github.com/stellar/stellar-dev-skill/pull/147">PR #147</a>, preserving Scopuly’s original commit.</p><p>This is a community listing, not an SDF security certification or endorsement. Scopuly maintains the skill, and developers remain responsible for reviewing the instructions and generated code they use.</p><p>The practical benefit is discoverability: another path from “I am building on Stellar” to “here is how I can integrate Scopuly.”</p><h3>Start by Installing the Skill</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gbp6VmUyRBORjK7lSdwybQ.png" /><figcaption>Give Your AI Coding Agent Scopuly Integration Context</figcaption></figure><p>From your development environment, run:</p><pre>npx skills add Scopuly/scopuly-skills --skill scopuly-wallet</pre><p>Follow the installer’s prompts for your supported coding agent and installation scope.</p><p>Alternatively, copy the skills/scopuly-wallet directory into your agent’s skills directory. Keep its references/ and assets/ folders alongside SKILL.md; they contain supporting material the instructions refer to.</p><p>The installation command and manual alternative are documented in the <a href="https://github.com/Scopuly/scopuly-skills#install">repository README</a>.</p><p>Installing the skill does not install Scopuly or connect a wallet. It gives the coding agent integration context. Testing still requires the appropriate wallet environment.</p><h3>Scenario 1: Add Scopuly to an Existing Stellar dApp</h3><p>A useful first task is adding Scopuly to an application that already uses Stellar Wallets Kit.</p><p>Instead of asking the agent to rebuild wallet management, make the existing architecture part of the request.</p><h3>Try this prompt</h3><blockquote><em>Use the scopuly-wallet skill to add Scopuly support to this React application.</em></blockquote><blockquote><em>First inspect our existing Stellar Wallets Kit setup and installed dependency versions. Keep the current wallet selector and connection architecture.</em></blockquote><blockquote><em>Add Scopuly using the appropriate built-in module. Handle wallet availability, user rejection, and network mismatch. When the account or network changes, clear any prepared transaction that is no longer valid.</em></blockquote><blockquote><em>Add relevant tests and explain which checks require a real wallet.</em></blockquote><p>This prompt gives the agent a defined task and clear constraints. It asks for integration with the application - not a second, competing connection manager.</p><p>The skill specifically directs agents to reuse an existing Wallets Kit integration when one is already present. <a href="https://github.com/Scopuly/scopuly-skills/blob/main/skills/scopuly-wallet/SKILL.md">Read the integration instructions</a>.</p><h3>What to review afterward</h3><p>Check that the implementation fits the existing user experience:</p><ul><li>Does Scopuly appear in the intended wallet-selection flow?</li><li>Does connecting require an explicit user action?</li><li>Is a network mismatch explained clearly?</li><li>Does rejecting a request return the interface to a usable state?</li><li>Does changing accounts invalidate the previous transaction preview?</li></ul><p>These checks are more useful than confirming that a Connect button renders.</p><h3>Scenario 2: Build a Direct Connect-and-Sign Example</h3><p>For a Scopuly-specific application, you can ask the agent to use the Provider API directly.</p><p>This is also a useful way to learn the boundary between the application and the wallet before adding more abstraction.</p><h3>Try this prompt</h3><blockquote><em>Use the scopuly-wallet skill to build a minimal React and TypeScript example with the direct Scopuly Provider API.</em></blockquote><blockquote><em>Detect the provider without opening an approval prompt. Request access only when the user clicks Connect.</em></blockquote><blockquote><em>Show the connected public address and wallet network. Use Testnet, prepare a self-payment, and let the user inspect the transaction before requesting a signature.</em></blockquote><blockquote><em>Verify the returned signed transaction and display its XDR. Do not submit it to the network.</em></blockquote><blockquote><em>Include clear states for a missing wallet, delayed provider injection, rejected requests, and account or network changes.</em></blockquote><p>The deliberately limited scope makes the result easier to inspect: connect, prepare, approve, and verify - without broadcasting a transaction.</p><p>For this flow, a typed SDK wrapper is not the wallet itself. The provider must be available through Scopuly’s supported browser environment; installing an npm package alone does not inject it. The skill makes that distinction explicit. <a href="https://github.com/Scopuly/scopuly-skills/blob/main/skills/scopuly-wallet/references/provider.md">Provider lifecycle reference</a>.</p><h3>Start with the included example</h3><p>The repository also includes a connect-and-sign example. With Node.js 24 or later:</p><pre>git clone https://github.com/Scopuly/scopuly-skills.git<br>cd scopuly-skills<br>npm ci<br>npm run dev</pre><p>Open the local URL in a browser with the paired Scopuly extension.</p><p>The example demonstrates connecting an account, signing and verifying a message, and signing a Testnet self-payment without submitting it. See the <a href="https://github.com/Scopuly/scopuly-skills/tree/main/examples/connect-sign">example source</a> for the implementation.</p><h3>Scenario 3: Ask AI to Review an Integration You Already Have</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4qzz_ws-kZy-Vb4Co3FBbQ.png" /><figcaption>Does Your Stellar Wallet Integration Handle More Than “Connect”?</figcaption></figure><p>The skill is not limited to generating new code. It can also provide context for reviewing an existing implementation.</p><p>That is especially useful when the happy path works but connection changes, rejected requests, or timeouts produce confusing behavior.</p><h3>Try this prompt</h3><blockquote><em>Review our Scopuly integration using the scopuly-wallet skill.</em></blockquote><blockquote><em>Trace connection, account and network changes, transaction preparation, signing, and submission.</em></blockquote><blockquote><em>Look for stale account state, missing listener cleanup, duplicate signing requests, unchecked error results, and places where signing is incorrectly treated as successful submission.</em></blockquote><blockquote><em>Report concrete findings with file references before making changes. Separate issues confirmed by code from behavior that needs real-device testing.</em></blockquote><p>This is a review request, not permission to silently rewrite the application.</p><p>It also asks the agent to distinguish evidence from assumptions - a useful habit whenever wallet behavior is involved.</p><p>For more specialized work, you can narrow the task further:</p><blockquote><em>Use the scopuly-wallet signing reference to review our Soroban authorization flow. Verify the input and output formats expected by Scopuly’s signAuthEntry method. Do not treat its returned signature as a complete signed authorization entry.</em></blockquote><p>The <a href="https://github.com/Scopuly/scopuly-skills/blob/main/skills/scopuly-wallet/references/signing.md">signing reference</a> documents these format distinctions. Small encoding assumptions can have large consequences for interoperability.</p><h3>A Better Prompt Includes Acceptance Criteria</h3><p>“Integrate Scopuly” describes a goal. Acceptance criteria explain what a satisfactory implementation must do.</p><p>You can append the following to any of the prompts above:</p><blockquote><em>Before finishing:</em></blockquote><ul><li>Run the relevant checks available in this project.</li><li>Test missing-provider and user-rejection behavior.</li><li>Check account and network changes during an in-flight request.</li><li>Confirm that outdated transaction data cannot be reused.</li><li>Check the interface on mobile and desktop.</li><li>List simulated tests separately from real-wallet tests.</li><li>Do not submit a transaction unless I explicitly request that step.</li></ul><p>These criteria do not guarantee a correct implementation, but they make the work easier to evaluate.</p><p>For the skill repository’s own example, the <a href="https://github.com/Scopuly/scopuly-skills/blob/main/docs/testing.md">device-testing checklist</a> provides a starting point for testing beyond simulated providers.</p><h3>AI Helps Build the Integration. The User Approves Signing.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GSiJy-YrFNKgMYCHE-n_vg.png" /><figcaption>AI Helps Build. You Approve Signing - With Scopuly on Stellar</figcaption></figure><p>The distinction is important.</p><p>The skill helps a coding agent understand how to implement wallet interactions. It does not grant the agent access to a wallet, install a signing key, or enable unattended payments.</p><p>Scopuly signing requests still go through the wallet’s approval interface.</p><p>The integration guidance also treats these as separate states:</p><p><strong>Prepared transaction → approved signature → submitted transaction → confirmed result.</strong></p><p>An application should not display “payment complete” merely because it received a signature. Likewise, a submission timeout should not automatically trigger another payment without checking what happened to the original transaction.</p><p>These boundaries belong in the implementation and in the interface - not just in a warning at the bottom of a page.</p><h3>From Instructions to a Working Integration</h3><p>Scopuly now offers complementary resources for different stages of development:</p><ul><li><strong>Stellar’s Wallet Integration guide</strong> helps developers discover the integration.</li><li><strong>Scopuly Wallet skill</strong> gives AI coding agents instructions and examples to work from.</li><li><strong>Connect Lab</strong> lets developers explore connection, signing, and submission in an interactive demo.</li></ul><p>The workflow is straightforward: give your agent the relevant context, define a focused task, review the implementation, and test it with the wallet.</p><p>We will continue maintaining the skill as the integration evolves. Developers can inspect the source, report gaps, and suggest examples that would make their work easier.</p><p>Thank you to the Stellar Skills maintainers for incorporating the community listing, and to the Stellar Wallets Kit maintainers for the tooling that supports multi-wallet applications.</p><p><strong>Start with the </strong><a href="https://github.com/Scopuly/scopuly-skills"><strong>Scopuly Wallet skill</strong></a><strong>, find it in </strong><a href="https://skills.stellar.org/"><strong>Stellar Skills</strong></a><strong>, and try a concrete task in your own application.</strong></p><p>For a walkthrough of the interactive demo, read our companion article: <a href="https://scopuly.medium.com/edf1d3d9fc98"><strong>From Connect to Confirmed: Build Your Stellar Wallet Integration with Scopuly</strong></a>.</p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52806675c984" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Connect to Confirmed: Build Your Stellar Wallet Integration with Scopuly]]></title>
            <link>https://scopuly.medium.com/from-connect-to-confirmed-build-your-stellar-wallet-integration-with-scopuly-edf1d3d9fc98?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/edf1d3d9fc98</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[defi]]></category>
            <category><![CDATA[scopuly]]></category>
            <category><![CDATA[digital-wallet]]></category>
            <category><![CDATA[stellar]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 08:28:23 GMT</pubDate>
            <atom:updated>2026-10-07T08:50:06.703Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IQjOheCXfaPyVA_lRpNn9w.png" /><figcaption>Build Beyond the Connect Button: Scopuly Opens the Full Stellar Transaction Journey</figcaption></figure><p><em>A hands-on, open-source demo for connecting a wallet, inspecting requests, signing transactions, and submitting them to Stellar.</em></p><p>A “Connect wallet” button is only the beginning.</p><p>What happens after the user clicks it? Which account does the application receive? Where does approval happen? What exactly gets signed - and when does that transaction reach the network?</p><p>These are the questions we wanted to make easier to answer with <strong>Scopuly Connect Lab</strong>, an open-source wallet integration demo built with React and TypeScript.</p><p>It brings the complete flow into one place:</p><p><strong>Connect → prepare → review and sign → submit → verify.</strong></p><p>You can try it, inspect the requests and responses, and explore the source code as a reference for your own Stellar application.</p><p><a href="https://extension.scopuly.com/connect-demo/">Launch Scopuly Connect Lab</a> · <a href="https://github.com/Scopuly/scopuly-connect-demo">Explore the source on GitHub</a></p><h3>One Demo, Three Integration Paths</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SBcntYyB_reubCguX0m2LQ.png" /><figcaption>Three Paths. One Complete Flow. Connect Your Stellar dApp with Scopuly.</figcaption></figure><p>Different applications need different ways to connect to a wallet. Connect Lab lets developers explore three approaches without switching between separate demos.</p><h3>Stellar Wallets Kit</h3><p>If your application supports multiple Stellar wallets, Stellar Wallets Kit provides a common integration interface.</p><p>Connect Lab demonstrates its Scopuly module, which communicates with the provider exposed by the Scopuly browser extension or Scopuly’s in-app browser.</p><p>This is a useful starting point when Scopuly is one of several wallet options in your application.</p><h3>Direct Provider API</h3><p>For applications that want to work directly with Scopuly, the Provider API exposes the wallet interface through window.scopuly.</p><p>This approach lets developers inspect Scopuly-specific calls without going through a multi-wallet abstraction. Connect Lab includes a dedicated Provider API mode so you can compare the direct integration with the Wallets Kit approach.</p><p>The <a href="https://extension.scopuly.com/docs/provider-api/">Provider API documentation</a> provides the interface reference.</p><h3>WalletConnect</h3><p>WalletConnect provides a separate connection path through a wallet session, without requiring the Scopuly browser extension.</p><p>In Connect Lab, this option uses the separately configured WalletConnect module. Developers running their own copy can supply their own Reown project ID.</p><p>These paths serve different integration needs, but the goal is the same: make account access and transaction approval understandable to both developers and users.</p><h3>Follow the Complete Transaction Lifecycle</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hv7HKTwoM5Se36lBtgi-HQ.png" /><figcaption>Sharing your public address does not authorize a dApp to sign transactions</figcaption></figure><p>Connect Lab is more than a connection test. It walks through the steps that come after account access, while keeping each action explicit.</p><h3>1. Connect your wallet</h3><p>Choose an integration method and connect Scopuly.</p><p>For the extension-based flow, make sure your extension is paired with a Scopuly signer and that the wallet is using the same network as the demo.</p><p>The extension connects the application to a paired Scopuly signer on iOS, Android, or macOS. It does not store secret keys or seed phrases in the browser extension.</p><p>Account access and transaction approval are separate steps. Sharing a public address does not grant permission to sign transactions automatically.</p><h3>2. Check the account and fund it on Testnet</h3><p>Testnet is selected by default.</p><p>After connecting, you can check the account’s balance and request test XLM through Stellar Friendbot. Test XLM has no monetary value, making Testnet the right place to explore the flow before using a funded Mainnet account.</p><p>This step also makes an important dependency visible: a connected wallet and an account ready to transact are not necessarily the same thing.</p><h3>3. Prepare a transaction</h3><p>The demo prepares a self-payment rather than an arbitrary transfer.</p><p>On Testnet, the example sends <strong>1 test XLM to your own address</strong>. On Mainnet, it sends <strong>0.01 XLM to your own address</strong>.</p><p>The destination is intentionally your connected account. This keeps the example focused on integration mechanics rather than recipient entry.</p><p>You can inspect the transaction details and unsigned XDR before requesting a signature.</p><h3>4. Review and sign in Scopuly</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9H7gujK7qPG5u6J0fzgM3Q.png" /><figcaption>Your Wallet. Your Approval. Scopuly Makes Every Stellar Signature an Explicit Step.</figcaption></figure><p>The application sends a signing request to the wallet.</p><p>You review the request in Scopuly and decide whether to approve it. Connect Lab then checks the returned signed transaction against the transaction it prepared before allowing submission.</p><p>Crucially, <strong>signing does not submit the transaction to Stellar</strong>.</p><p>This distinction is easy to miss in a compact code example. In Connect Lab, it is a visible part of the interface.</p><h3>5. Submit and verify</h3><p>Submission requires a separate action.</p><p>Once the signed transaction is submitted successfully, the demo displays the transaction hash and a link to the corresponding Stellar explorer.</p><p>That closes the loop: you can follow a request from the application, through wallet approval, to its result on the network.</p><h3>See What Happens Under the Hood</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JqOR45hXvW_hZn07odPlvA.png" /><figcaption>From API Call to On-Chain Confirmation: See Inside Your Stellar Integration with Scopuly</figcaption></figure><p>A useful integration example should explain more than which button to click.</p><p>Connect Lab includes a developer panel with:</p><ul><li>Code examples for the selected integration method.</li><li>Request and response data.</li><li>An activity log for following the sequence of calls.</li><li>Transaction XDR available for inspection during the flow.</li></ul><p>This makes it easier to connect an interface action with the API call behind it.</p><p>If something fails, you have a clearer starting point for investigation: was the issue with connection, account loading, transaction preparation, signing, or submission?</p><p>The distinction matters. A wallet connection can succeed while a later step fails for an entirely different reason.</p><p>The code examples provide a compact introduction; the repository contains the surrounding implementation and checks.</p><h3>Testnet First, Mainnet When You Choose</h3><p>Testnet is the default, but Connect Lab also supports Mainnet.</p><p>The Mainnet example is deliberately limited to a <strong>0.01 XLM self-payment</strong>. The payment amount returns to the same account; a successful transaction still consumes a real network fee.</p><p>The demo currently sets a maximum transaction fee of <strong>1,000 stroops, or 0.0001 XLM</strong>, for this single-operation example.</p><p>Mainnet is therefore not a free test environment. Always review the selected network, account, transaction, and fee before approving and submitting.</p><p>For developers, supporting both networks also makes network handling visible. A transaction must be prepared, signed, and submitted using consistent network settings - not merely displayed under the right label.</p><h3>Use the Source as a Starting Point</h3><p>Connect Lab is open source, with a React and TypeScript implementation available on GitHub.</p><p>You can run it locally, explore the adapters, and see how connection state, transaction preparation, wallet approval, and submission fit together.</p><p>It is a reference implementation, not a substitute for the requirements of your own application. A production integration still needs appropriate testing, error handling, and security review for its particular transaction types and users.</p><p>We hope the demo makes those next steps easier by providing a concrete flow to inspect and adapt.</p><p><a href="https://github.com/Scopuly/scopuly-connect-demo">View the Scopuly Connect Lab repository</a></p><h3>Scopuly Is Also in Stellar’s Developer Documentation</h3><p>Alongside the demo, our contribution to the official Stellar developer documentation has been merged.</p><p>The Wallet Integration guide now includes Scopuly in the Stellar Wallets Kit wallet list and provides a dedicated Scopuly section linking to the extension, Provider API, and extension source code.</p><p>That gives developers another place to discover the integration and find its supporting resources.</p><p><a href="https://developers.stellar.org/docs/tools/developer-tools/wallets#scopuly">Read the Scopuly section in Stellar Docs</a> · <a href="https://github.com/stellar/stellar-docs/pull/2878">View the merged contribution</a></p><p>Thank you to the Stellar Wallets Kit maintainers for their work and help with the Scopuly integration, and to the Stellar Docs maintainers for reviewing and merging our documentation contribution.</p><h3>Try It - and Tell Us What Would Help You Build</h3><p>Our goal is straightforward: make the path from wallet connection to a confirmed Stellar transaction easier to understand.</p><p>If you are integrating wallets into a Stellar dApp, try Connect Lab and let us know where the experience could be clearer.</p><p>Useful feedback includes the integration method, browser or platform, selected network, and the step where something fails. Please never include private keys or seed phrases in a report.</p><p><strong>Start on Testnet. Inspect each step. Then use the source to build your own integration.</strong></p><p><a href="https://extension.scopuly.com/connect-demo/">Try Connect Lab</a></p><p><a href="https://github.com/Scopuly/scopuly-connect-demo">Explore the source code</a></p><p><a href="https://extension.scopuly.com/docs/provider-api/">Read the Provider API documentation</a></p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edf1d3d9fc98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scopuly Agents on Stellar: Give AI a Task. Keep Control of the Budget.]]></title>
            <link>https://scopuly.medium.com/scopuly-agents-on-stellar-give-ai-a-task-keep-control-of-the-budget-da1f8a87e596?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/da1f8a87e596</guid>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[x402]]></category>
            <category><![CDATA[scopuly]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 19:45:27 GMT</pubDate>
            <atom:updated>2026-09-26T19:45:27.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MqHOQLKq3wGbWIgtINP_6g.png" /><figcaption>Scopuly Agents on Stellar: Give AI a Task. Keep Control of the Budget.</figcaption></figure><h3>Previewing a wallet interface for useful tasks, limited spending permissions, and transparent purchase records.</h3><p>What if you could give an AI agent a research task - and decide exactly which services it could use, how much it could spend, and when its permission should end?</p><p>That is the experience we are exploring with <strong>Scopuly Agents</strong>.</p><p>We have built an interactive interface covering task creation, spending limits, permissions, purchases, recovery, and results. It makes the proposed experience tangible before connecting it to an autonomous execution system.</p><p><strong>This is a product preview, not a live agent launch. The screens use illustrative data and simulated purchases. They do not make AI requests, authorize real spending, or create on-chain permissions.</strong></p><p>Here is what we have designed - and where we want to take it next.</p><h3>Start With a Task, Not a Payment</h3><p>Most people do not begin with “I want to buy an API response.”</p><p>They begin with a question.</p><p>Explain my Stellar account. Gather information about network activity. Collect the resources needed to understand a particular topic.</p><p>The proposed Scopuly flow starts with that intent. A user describes a task, selects allowed services, and reviews the spending boundaries before proceeding.</p><p>The interface explores two entry points:</p><ul><li><strong>Scopuly agent:</strong> create a task inside Scopuly.</li><li><strong>External agent:</strong> review a connection request from another application.</li></ul><p>Both paths lead to the same central question: what should this agent be allowed to do?</p><p>External-agent connections are also simulated in this preview; the interface does not yet connect to partner agents.</p><h3>A Budget Is a Ceiling, Not a Spending Target</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wavIdffmfyaylAcqBqzXJw.png" /><figcaption>Scopuly Agents on Stellar: Your Budget Sets the Boundary</figcaption></figure><p>An agent should not interpret an available budget as an instruction to spend it all.</p><p>The permission interface brings together:</p><ul><li>a total task budget;</li><li>a maximum amount per request;</li><li>an explicit list of allowed services;</li><li>an expiration time;</li><li>controls to pause or revoke permission.</li></ul><p>Automatic top-ups are outside the proposed initial scope. So are trading and unrestricted transfers.</p><p>In the illustrative scenario, a task starts with a <strong>1 USDC allowance</strong>. One simulated resource purchase costs <strong>0.01 USDC</strong>, leaving <strong>0.99 USDC</strong> available.</p><p>That remaining allowance is not a deposit waiting to be refunded. It represents unused spending capacity.</p><p>The current design also distinguishes resource purchases from AI usage and network fees. Those costs need an explicit pricing policy before a live release - not an assumption that everything fits inside one displayed number.</p><h3>When a Request Exceeds the Rules, Ask</h3><p>Some requests should stop for a decision.</p><p>The preview includes a purchase that exceeds the per-request limit. Instead of silently increasing the allowance, the interface presents a one-time approval request.</p><p>The intended distinction is important:</p><p><strong>Approving one purchase should not expand the agent’s future permissions.</strong></p><p>The total budget, allowed services, and expiration remain separate boundaries. A user can approve an eligible request once or skip it.</p><p>These interactions currently demonstrate the proposed behavior. Production enforcement still needs to exist independently of the interface.</p><h3>An Interrupted Response Should Not Mean “Pay Again”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*urqz6rVMvQ_EA5aiO1ym5A.png" /><figcaption>Scopuly Agents on Stellar: Ask Before Exceeding the Rules</figcaption></figure><p>A connection can fail after a payment has been submitted but before a result reaches the user.</p><p>The Agents preview makes room for that uncertainty.</p><p>It distinguishes between a purchase whose payment outcome is unknown and one whose payment is recorded but delivery remains pending. An unresolved amount stays reserved in the simulated budget while recovery is demonstrated.</p><p>The design principle is straightforward: establish what happened to the original purchase before asking for another authorization.</p><p>This is a recovery experience we intend to support - not a claim that recovery already works across every external service.</p><h3>A Result Should Explain Its Evidence and Its Cost</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iVBmlr48TNIfJ4hiaeqB1Q.png" /><figcaption>Scopuly Agents on Stellar: See What a Task Actually Delivered</figcaption></figure><p>The updated <strong>Task result</strong> screen brings the task back into focus.</p><p>It shows the collected resource count, resource spending, remaining allowance, source coverage, and links to purchase receipts.</p><p>It also makes missing information visible. Allowing an agent to use a service does not mean that a resource was actually obtained from it.</p><p>Two distinctions matter here:</p><p><strong>A purchase timestamp is not proof of fresh source data.</strong></p><p><strong>A delivered purchase is not proof of an accurate answer.</strong></p><p>The preview therefore includes coverage gaps and data limitations alongside the purchase records. It does not invent network measurements or present a generated research conclusion. A copyable report preserves the illustrative-data disclosure.</p><h3>What Comes Next</h3><p>The next milestone is connecting this interface to a narrow, useful, user-approved workflow.</p><p>That requires more than adding a model API. The live system needs durable tasks, recoverable results, independently enforced budgets, scoped authorization, and a clear policy for data sent to external providers.</p><p>Our intended progression is:</p><ol><li>Complete a useful task with explicit approval for paid requests.</li><li>Verify the relationship between payment, receipt, and delivered resource.</li><li>Support recovery across interruptions and restarts.</li><li>Introduce carefully bounded automation after its authorization and security controls have been validated.</li></ol><p>The model may propose a purchase. It should not be able to grant itself permission, increase its budget, or bypass the user’s limits.</p><h3>Making Agent Spending Understandable</h3><p>The opportunity is larger than putting a chatbot inside a wallet.</p><p>A wallet can help people understand what software is asking to buy, decide whether it should proceed, and inspect what happened afterward.</p><p>Scopuly Agents is our preview of that experience: a task, clear boundaries, visible purchases, and a result whose limitations remain understandable.</p><p><strong>The interface is ready to explore. Autonomous execution and budgeted payments are not live yet.</strong></p><p>As the implementation develops, we want to hear which task would make this genuinely useful to you - and what you would need to see before trusting an agent with a spending allowance.</p><h3>Explore More: Scopuly and x402 on Stellar</h3><p>Follow the building blocks behind Scopuly’s agent-payment direction:</p><ul><li><a href="https://scopuly.medium.com/scopuly-joins-stellars-x402-wallet-list-and-builds-toward-agent-payments-033c1365b723"><strong>Scopuly Joins Stellar’s x402 Wallet List - and Builds Toward Agent Payments</strong></a><br>Our wallet integration, mobile approval experience, and direction for agent payments.</li><li><a href="https://scopuly.medium.com/scopuly-ai-payments-pay-for-ai-requests-with-usdc-on-stellar-70c96315a22d"><strong>Scopuly AI Payments: Pay for AI Requests with USDC on Stellar</strong></a><br>Exploring user-approved AI purchases paid in Stellar USDC.</li><li><a href="https://scopuly.medium.com/pay-once-recover-on-another-device-scopulys-x402-recovery-on-stellar-1693a330dd43"><strong>Pay Once, Recover on Another Device: Scopuly’s x402 Recovery on Stellar</strong></a><br>Recovering an existing purchase across browsers and devices without authorizing another payment.</li></ul><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da1f8a87e596" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pay Once, Recover on Another Device: Scopuly’s x402 Recovery on Stellar]]></title>
            <link>https://scopuly.medium.com/pay-once-recover-on-another-device-scopulys-x402-recovery-on-stellar-1693a330dd43?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/1693a330dd43</guid>
            <category><![CDATA[x402]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[agentic-payment]]></category>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[scopuly]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 18:24:43 GMT</pubDate>
            <atom:updated>2026-09-26T18:24:43.638Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y0Knwc4mlRsBCIOhX4Vsrg.png" /><figcaption>Scopuly x402: Pay on Desktop, Recover on Mobile with Stellar</figcaption></figure><p><em>From a desktop purchase to mobile recovery - with a portable purchase reference, wallet-ownership proof, and no new payment.</em></p><p>A payment can succeed even when the user never receives the result.</p><p>A connection drops. A browser closes. A response disappears somewhere between the service and the screen. For the user, the question is simple: “I already paid. How do I get what I purchased?”</p><p>In our previous article, we described how Scopuly’s x402 demo handles interrupted purchases within the same browser storage and account. The demo saves a purchase reference before signing, checks unresolved attempts, and can retry delivery after settlement is confirmed.</p><p>Then someone in the community asked a useful follow-up: could that purchase reference move to another device?</p><p>We have now implemented that next step - and tested recovery across desktop browsers and from desktop to Scopuly Mobile on Stellar Mainnet.</p><h3><strong>A purchase should not depend on keeping one browser open</strong></h3><p>Local browser storage helps preserve a purchase through a refresh or an interrupted connection. But another browser does not automatically have that history. Neither does a phone.</p><p>To recover an existing purchase elsewhere, the user needs a way to identify it - and the service needs a way to decide whether that user is entitled to receive its result.</p><p>Those are separate responsibilities.</p><p>A purchase reference answers: <strong>Which purchase are we talking about?</strong></p><p>A wallet proof answers: <strong>Can this requester demonstrate control of the wallet that paid?</strong></p><p>Scopuly’s recovery flow uses both. The reference can travel as a link or QR code. Possession of that reference alone does not authorize access to the purchased result.</p><h3><strong>What we tested on Mainnet</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9mNp7N_U7tXFwSnZSN7tig.png" /><figcaption>Scopuly x402 Recovery: Original Purchase, Same Stellar Transaction</figcaption></figure><p>Our test began with a <strong>0.001 USDC purchase</strong> in Scopuly’s x402 demo through desktop Chrome.</p><p>We copied its recovery link and opened it in Chrome Canary, using a separate browser environment. After connecting the same paying wallet through the Scopuly extension and mobile app, we requested recovery and approved a message with the wallet.</p><p>The demo returned the existing purchase with its original receipt and saved result. The recovery output reported:</p><pre>{<br>  &quot;recovered&quot;: true,<br>  &quot;paidRequestSent&quot;: false,<br>  &quot;status&quot;: &quot;delivered&quot;<br>}</pre><p>The receipt and returned settlement details referenced the same original transaction.</p><p>We then tested the mobile path: opening the demo inside Scopuly Mobile, providing the purchase reference, and confirming recovery with the same wallet. That test also succeeded.</p><p>The practical result is straightforward: a purchase started on a computer can be recovered on a phone without authorizing another payment.</p><h3><strong>A recovery signature is not a spending permission</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y34jUpeycoxsP8a_h8T9eA.png" /><figcaption>Scopuly x402 on Stellar: Prove Wallet Ownership Without Paying Again</figcaption></figure><p>The wallet does not sign another payment to recover the result.</p><p>Instead, the server issues a short-lived message identifying the recovery action, service domain, network, purchase, and wallet. The message also includes a unique nonce and an expiry time.</p><p>Its purpose is stated explicitly:</p><blockquote><em>No payment or spending permission is authorized.</em></blockquote><p>The server verifies the signature, checks the account’s current signing configuration, and consumes the challenge once. An expired or previously consumed challenge cannot authorize another recovery request; the user must obtain a fresh challenge.</p><p>This distinction matters for the approval experience. A user retrieving something already purchased should see a request to prove wallet ownership, with the relevant purchase context.</p><p>After successful verification, the server returns the stored result - or attempts delivery for a purchase whose settlement is already confirmed. The recovery path does not initiate another payment settlement.</p><h3><strong>How to try it</strong></h3><p>Start with an existing purchase in the <a href="https://app.scopuly.com/x402-demo/">Scopuly x402 Mainnet demo</a>.</p><ol><li>Connect the wallet that paid and select <strong>Copy my latest recovery link</strong>.</li><li>Open the link in another supported desktop browser, or open the demo inside <strong>Scopuly Mobile</strong> and paste the link into the recovery field.</li><li>Connect the same wallet.</li><li>Select <strong>Recover purchase · No payment</strong>.</li><li>Review and sign the recovery message.</li></ol><p>The result should identify the original purchase and its transaction.</p><p>On a phone, the demo must run inside Scopuly’s built-in dApp browser for this flow. Scanning the QR with the phone’s ordinary camera may open the default browser, where the Scopuly provider is unavailable. The current QR transfers the reference; it does not automatically open the recovery screen inside the wallet.</p><h3><strong>What this release covers</strong></h3><p>This first implementation supports purchases from Scopuly’s own x402 demo on Stellar Mainnet and accounts with a single active master signer.</p><p>It does not yet provide recovery for arbitrary x402 services, external AI purchases, multisignature accounts, or accounts with rotated or disabled master keys. It also does not automatically discover every previous purchase when a user connects a wallet on a new device. Users need to retain their purchase reference.</p><p>The result is stored by the service. The blockchain records the payment, but it does not reconstruct the purchased response if the service no longer retains it. Recovery therefore depends on the continued availability of the purchase record and its saved result.</p><p>These boundaries are part of the feature’s design and documentation.</p><h3><strong>Making payment recovery part of the experience</strong></h3><p>A successful payment is only one part of a successful purchase.</p><p>Users also need to understand what happened when delivery was interrupted, whether a payment is still unresolved, and how to retrieve an existing result after changing browsers or devices.</p><p>For Scopuly, portable recovery extends the work we began with explicit mobile approval and retry handling. It gives users a concrete way to return to an existing purchase while keeping access tied to their wallet.</p><p>The community question gave us a useful next test. We now have a working desktop-to-mobile recovery flow - and a clearer foundation for improving the experience further.</p><p><strong>Try it:</strong> <br><a href="https://app.scopuly.com/x402-demo/">Scopuly x402 Mainnet Demo</a></p><p><strong>Read the previous chapter:</strong> <br><a href="https://medium.com/p/033c1365b723">Scopuly Joins Stellar’s x402 Wallet List - and Builds Toward Agent Payments</a> explores our mobile approval flow, the original recovery approach, and the direction of Scopuly’s agent payment work.</p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1693a330dd43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scopuly AI Payments: Pay for AI Requests with USDC on Stellar]]></title>
            <link>https://scopuly.medium.com/scopuly-ai-payments-pay-for-ai-requests-with-usdc-on-stellar-70c96315a22d?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/70c96315a22d</guid>
            <category><![CDATA[x402]]></category>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[scopuly]]></category>
            <category><![CDATA[usdc]]></category>
            <category><![CDATA[ai-payment]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 06:19:22 GMT</pubDate>
            <atom:updated>2026-09-21T06:19:22.845Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F_hcREA-_hvxWgDfB8SgrA.png" /><figcaption>Scopuly AI Payments: Pay for AI Requests with USDC on Stellar</figcaption></figure><p><em>An AI request, a price you can review, and a payment you approve in your wallet. Now available through the Scopuly browser extension.</em></p><p>Scopuly AI Payments is live.</p><p>You can submit an AI prompt, fetch its price, approve a USDC payment through Scopuly, and receive the response on the same page. Payments settle on Stellar Mainnet through MPP Router, built by Rozo.</p><p>The current experience connects to OpenAI’s GPT-4o-mini through the router. You do not need to supply your own OpenAI API key or subscribe to an AI plan to make a request through this integration.</p><p><a href="https://app.scopuly.com/ai-payments/"><strong>Try Scopuly AI Payments →</strong></a></p><h3>From a prompt to a wallet-approved payment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xusOZepwCl-VOX5ICXn9MA.png" /><figcaption>Connect Scopuly: Bring Stellar Payments to Your AI Requests</figcaption></figure><p>The experience follows a straightforward sequence:</p><ol><li><strong>Write your request.</strong> Enter a prompt and choose the response length.</li><li><strong>Connect Scopuly.</strong> Connect your wallet through the browser extension.</li><li><strong>Fetch the price.</strong> Review the current quote before authorizing anything.</li><li><strong>Approve the payment.</strong> Confirm the request in Scopuly.</li><li><strong>Read the answer.</strong> View the response alongside its payment status and transaction details.</li></ol><p>Each new purchase requires your approval.</p><p>During smoke testing, the recommended short request was quoted at <strong>0.001 USDC</strong>. Prices can change: the fresh quote shown before approval is authoritative. The current Scopuly page enforces a maximum of <strong>0.008 USDC per request</strong>, with sponsored network fees for this integration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rfbynGPJBx5-o-esZ6ggNA.png" /><figcaption>Scopuly Makes Every Stellar AI Payment a Decision You Review</figcaption></figure><p>Prompts are sent to MPP Router and the AI provider. Wallet secrets, recovery phrases and private keys should never be included in a prompt.</p><h3>Why this matters for Stellar developers</h3><p>This integration demonstrates a concrete use for Stellar payments: purchasing an individual API response from a wallet.</p><p>A developer can build an interface that brings the service request, payment approval and result together. Users see what they are about to pay for, while the wallet remains responsible for approving the payment.</p><p>The responsibilities are clear:</p><ul><li><strong>Scopuly</strong> provides the wallet connection and approval experience.</li><li><strong>MPP Router</strong> coordinates access to the paid service and the payment flow.</li><li><strong>Stellar</strong> provides the on-chain settlement record.</li><li><strong>The AI provider</strong> processes the request.</li></ul><p>Scopuly is now listed in the <strong>Wallet app</strong> section of <a href="https://www.mpprouter.dev/how-it-works#use-with-agents">MPP Router’s integration directory</a>, with a link to the permanent AI Payments page.</p><p>For developers exploring paid APIs, this gives them a working example to try before building their own experience.</p><h3>A payment needs more than a success screen</h3><p>The difficult cases start when a request does not finish cleanly.</p><p>A wallet approval can take time. A network connection can disappear after a payment is submitted. A provider can reject a request. A response can arrive without usable text.</p><p>Scopuly AI Payments includes payment history, recovery and verification to help users understand these outcomes.</p><p><strong>Payment history is stored locally in encrypted form.</strong> It belongs to that browser and does not automatically sync between devices. Returning users reconnect the original wallet to access the relevant records.</p><p><strong>An interrupted response can be recovered using the original payment credential</strong>, where the router’s recovery rules allow it. Recovery preserves the original URL, request body and exact payment signature; it does not ask the user to authorize a second payment for the same recovery attempt.</p><p>This recovery behavior is specific to MPP Router. Developers should not assume that every server using HTTP 402 or x402 provides the same mechanism.</p><p><strong>Unresolved payments remain blocked from unsafe repeat purchases.</strong> An uncertain response is not treated as proof that no money moved.</p><h3>Verifying refunds</h3><p>Refund reconciliation is also part of the implementation.</p><p>When the router reports a refund, Scopuly stores the refund ID and status URL together with the original Stellar payment transaction hash. The <strong>Check refund</strong> action then checks the router’s status.</p><p>For a completed full refund, the application:</p><ul><li>Verifies the receipt’s Ed25519 signature against a current or retired signer published by MPP Router.</li><li>Checks the original payment and refund independently on Stellar.</li><li>Confirms that the expected asset and amount were returned to the original payer.</li><li>Resolves the affected payment only after those checks succeed.</li></ul><p>A pending status alone does not count as a confirmed refund.</p><p>The implementation has passed automated tests, browser recovery tests and verification against a real historical refund published by the router. A separate controlled mainnet test covering a newly initiated payment, service failure and refund remains the next validation step.</p><h3>What we learned from real payments</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O64_wZP7VFiAAmzIalTVgg.png" /><figcaption>Scopuly AI Payments: A Stellar Payment and an AI Answer Need Separate Checks</figcaption></figure><p>Our initial mainnet testing surfaced an important distinction: <strong>a settled payment and a useful AI answer are separate things to verify</strong>.</p><p>One early request used a reasoning model with a small output budget. The model consumed almost all of that budget on reasoning and returned no visible answer. Shawn and the Rozo team traced the upstream response and confirmed that the request had been delivered and paid.</p><p>They also identified a provider-response wrapper that the parser needed to handle.</p><p>Those findings helped shape the current experience: a simpler initial model choice, clearer response handling, and payment status presented separately from the answer itself.</p><h3>Available now, with mobile availability to follow</h3><p><strong>Browser extension approval is available now.</strong></p><p>We have also completed manual testing in the Scopuly iPhone in-app browser. The updated mobile release will become available through the stores later; those tests should not be read as a claim that every currently installed mobile version already supports the updated flow.</p><p>The current product focuses on individual requests approved by the user. Autonomous Scopuly Agents and session-based spending are outside this release.</p><p>Provider availability can depend on region. Users should review the live quote and the payment result for each request.</p><h3>Try it - or build on the experience</h3><p>Start with a short prompt, fetch the price, and review the payment in your wallet.</p><p><a href="https://app.scopuly.com/ai-payments/"><strong>Open Scopuly AI Payments →</strong></a></p><p>For developers who want to explore further:</p><ul><li><a href="https://app.scopuly.com/x402-demo/">Scopuly x402 demo</a></li><li><a href="https://extension.scopuly.com/playground/">Scopuly developer playground</a></li><li><a href="https://extension.scopuly.com/">Scopuly browser extension</a></li><li><a href="https://www.mpprouter.dev/integration.md">MPP Router integration documentation</a></li><li><a href="https://scopuly.com/">Explore Scopuly</a></li></ul><p>Thank you to Shawn and the Rozo team for their support with the integration, upstream diagnostics and refund-verification details.</p><p>We look forward to seeing what developers build when an API request can carry a clear price - and a payment the user approves in their own wallet.</p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70c96315a22d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scopuly Is Building Native USDC Transfers Between Stellar and Other Blockchains with Circle CCTP]]></title>
            <link>https://scopuly.medium.com/scopuly-is-building-native-usdc-transfers-between-stellar-and-other-blockchains-with-circle-cctp-4dd13183041e?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/4dd13183041e</guid>
            <category><![CDATA[usdc]]></category>
            <category><![CDATA[cctp]]></category>
            <category><![CDATA[scopuly]]></category>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[circle]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 17:11:46 GMT</pubDate>
            <atom:updated>2026-09-14T17:11:46.667Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-3-c_n3YXNogOaPTVT7xFA.png" /><figcaption>Scopuly is building native USDC transfers between Stellar and other networks with Circle CCTP, now in controlled beta.</figcaption></figure><p><em>From technical design to an implemented wallet flow connecting Stellar with other USDC networks.</em></p><p>A user holding USDC on Base may want to make a payment, trade, or manage that balance on Stellar. Getting there involves more than choosing a destination address: the wallet needs to explain the network, prepare the account, show the costs, and help the user follow a transfer across two blockchains.</p><p>We have started building that experience directly into Scopuly with Circle’s Cross-Chain Transfer Protocol, or CCTP.</p><p>The first CCTP milestone in our Stellar Community Fund roadmap called for a technical design and initial user-flow screens. Development has already progressed into transaction execution code, a connected wallet interface, transfer recovery, and deployed monitoring infrastructure.</p><p>The integration is in controlled beta. This article explains the current implementation and the validation work that comes next.</p><h3>Why CCTP fits this wallet experience</h3><p>CCTP moves native USDC between supported blockchains through three stages:</p><ol><li><strong>Burn:</strong> the user authorizes a transaction that burns USDC on the source network.</li><li><strong>Attest:</strong> Circle’s attestation service signs a message confirming the burn at the required confirmation level.</li><li><strong>Mint:</strong> the destination contracts verify that attestation and mint native USDC on the receiving network.</li></ol><p>This follows Circle’s <a href="https://developers.circle.com/cctp/references/technical-guide">CCTP technical architecture</a>.</p><p>For a Stellar wallet, the result is useful: users can bring native USDC into their Stellar account without receiving a wrapped substitute. Stellar’s documentation describes this native transfer model in its <a href="https://developers.stellar.org/docs/tokens/cross-chain-transfers">CCTP integration overview</a>.</p><p>Our work focuses on turning that protocol into an understandable wallet journey, from selecting an account to completing the receiving transaction.</p><h3>What the current implementation covers</h3><p>The development build includes these routes:</p><ul><li><strong>Stellar ↔ Base, Ethereum, Arbitrum, and OP Mainnet.</strong></li><li><strong>Solana → Stellar.</strong></li></ul><p>Both mainnet and testnet configurations are implemented. Stellar → Solana remains outside the current scope.</p><p>The interface includes account and network selection, external wallet connection, transfer estimates, review and signing screens, progress tracking, saved drafts, history, and recovery by source transaction hash.</p><p>These screens are connected to execution modules for EVM networks, Solana, and Stellar. The code prepares transactions, requests wallet authorization, reads blockchain confirmations, retrieves Circle attestations, and prepares the destination receiving step. Completed end-to-end transfers remain part of the upcoming acceptance process.</p><h3>A transfer, from the user’s perspective</h3><p>Consider the Base → Stellar route. The current flow guides the user through six steps.</p><h3>1. Choose the route</h3><p>The user selects Base as the source network and chooses a Stellar account already connected to Scopuly. Network selection is also available inside the connection flow, so the default network does not lock the user into a route.</p><h3>2. Connect the external wallet</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gDaUc41BnqyAv1hoVxPJ2A.png" /><figcaption>Connect your external wallet and prepare a USDC transfer to Stellar. Sending funds requires separate approval.</figcaption></figure><p>The connection screen offers detected browser wallets and WalletConnect. It includes MetaMask and Coinbase Wallet browser-provider paths, alongside a QR option for connecting a compatible wallet on another device. Solana routes use Solana-compatible connection options.</p><p>Preparing a connection has a visible loading state. Expired requests can be replaced, and an unsuccessful wallet handoff leads to instructions the user can act on.</p><p>Connecting an external wallet does not transfer funds. Transaction approval remains a separate action.</p><h3>3. Check account readiness</h3><p>Scopuly checks the selected Stellar account, its native USDC balance, and whether it has the required USDC trustline. When setup is needed, the interface offers a separate preparation flow with user confirmation.</p><p>This brings an important prerequisite into the transfer journey: the receiving account must be ready before the user sends USDC from another network.</p><h3>4. Review the amount and costs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZpWX9cMe12BfWZ1lDp90w.png" /><figcaption>Review the route, amount, and estimated costs before authorizing your native USDC transfer to Stellar.</figcaption></figure><p>The user enters an amount and sees an estimate of the USDC they will receive, the minimum receive amount under the quoted fee limit, and the protocol fee.</p><p>Network fees are explained separately. The current implementation expects the user to pay the relevant network costs, including the destination transaction.</p><p>Standard transfers are supported, with Fast offered on eligible inbound routes when Circle’s current fee and allowance responses permit it. Quotes are checked again before sending; changed conditions require a new review.</p><h3>5. Authorize the source transaction</h3><p>For the EVM route, a spending approval is requested if the existing allowance is insufficient. That approval is limited to the selected amount. The source burn then requires its own wallet authorization.</p><p>Before the burn request, the implementation checks the connected account and network, simulates the transaction, and checks available gas. The transfer intent is saved so the application has a record to recover if the wallet or network response is interrupted.</p><h3>6. Follow progress and receive USDC</h3><p>After source confirmation, the interface tracks the Circle attestation stage. When the message is ready, it presents the destination receiving action.</p><p><strong>The current flow requires the user to confirm this receiving transaction.</strong> Scopuly prepares the Stellar transaction and shows its network fee before signing.</p><p>The transfer record connects the source and destination stages, with transaction references and status information available in the wallet.</p><h3>The architecture behind the screens</h3><h3>The wallet prepares and verifies the transfer</h3><p>Scopuly coordinates the account, route, amount, quote, and signing steps. It verifies that the CCTP message matches the saved transfer, including the networks, token, sender, recipient, amount, and fee limit.</p><p>For incoming Stellar transfers, we use Circle’s official CctpForwarder contract. The final Stellar account is encoded in the forwarding data, and mint_and_forward delivers the minted USDC to that account. This follows Circle’s <a href="https://developers.circle.com/cctp/references/stellar">Stellar integration guidance</a>.</p><p>The implementation also handles the precision difference between Stellar’s seven-decimal USDC representation and CCTP’s six-decimal message amounts. Monetary calculations use integer units, avoiding floating-point rounding in transaction amounts.</p><h3>Circle provides the protocol and attestation</h3><p>The client retrieves the attestation used for receiving directly from Circle and checks the message against the transfer intent. The official destination contracts verify the attestation when processing the receiving transaction.</p><h3>Scopuly’s service monitors public transfer state</h3><p>A separate monitoring service verifies supported source transactions and follows their progress. Mainnet and testnet use separate processes and databases; the client also separates their drafts and histories.</p><p>The monitor stores public transaction information. It does not hold user keys, sign transfers, or pay gas. Its status response is not used as authorization to sign a transaction.</p><p>Both deployed environment APIs reported active workers during our September 14, 2026 development check. That confirms monitoring infrastructure is running; completed transfer validation is a separate step.</p><p><strong>Scopuly is not launching or operating its own Stellar anchor.</strong> Our role is wallet integration, user authorization, transaction verification, and progress tracking.</p><h3>Recovery is part of the transfer design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvNS5PEUSyFtaI999wJb5g.png" /><figcaption>Follow transfer progress, find an existing transfer by its source transaction hash, and continue the receiving step on Stellar.</figcaption></figure><p>A cross-chain transfer can outlast an app session. A wallet can close, an RPC request can time out, or the user can return after the source transaction has already been submitted.</p><p>We have built persistence and recovery around those situations:</p><ul><li><strong>Saved drafts</strong> let users leave before sending and continue later.</li><li><strong>Transfer records</strong> preserve the submitted amount, recipient, network, and transaction references.</li><li><strong>Find a transfer</strong> uses the source transaction hash to locate and verify a supported CCTP transfer.</li><li><strong>Uncertain submission states</strong> direct the user to check the existing transaction before starting another burn.</li><li><strong>Receiving retries</strong> continue the original transfer when its destination step needs attention.</li></ul><p>The interface distinguishes “Awaiting confirmation,” “Ready to receive,” “Receiving USDC,” and “Completed.” It also separates a declined source signature from a submitted transaction whose result is still unknown.</p><p>Expiration needs similar care. An expired wallet connection request does not mean USDC was sent. An expired quote needs a fresh estimate. A post-burn attestation that needs refreshing belongs to recovery of the existing transfer.</p><p>These distinctions help the user understand both the current state and the next available action.</p><h3>Designed for Scopuly’s platforms</h3><p>Scopuly is available on web, iOS, Android, and macOS. The CCTP connection flow accounts for the different ways those environments interact with external wallets: browser providers, mobile app handoffs, and QR connections from desktop.</p><p>The interface follows Scopuly’s existing components, supports light and dark themes, and uses the user’s selected primary color. Account balances have explicit loading and refresh states, while help is available within the flow.</p><p>Responsive browser checks have covered mobile and desktop layouts. Signing and returning from external wallets still need acceptance testing in the target native release builds.</p><h3>How this advances our first SCF milestone</h3><p>The first tranche defines the CCTP deliverables as a technical design for native USDC movement into Stellar and initial wireframes or prototype screens.</p><p>Our work now gives that design a concrete implementation: a navigable wallet flow, network-specific transaction modules, account-readiness checks, fee review, monitoring, and recovery. We have also implemented the reverse direction for the four selected EVM networks.</p><p>Coverage includes message validation, amount precision, supported routes, wallet connection behavior, persistence, monitoring, RPC handling, and interface state logic. These checks exercise controlled scenarios, with live transfer evidence to be added during acceptance.</p><p>This article documents the CCTP portion of that progress. MoneyGram remains a separate integration within the same roadmap, with its own working-MVP and demonstration requirements.</p><h3>What comes next</h3><p>The next acceptance stage will exercise the full <strong>burn → attestation → mint</strong> sequence with owner-authorized testnet transfers, record source and destination transaction hashes, and reconcile the resulting balances. It will also cover interrupted sessions, rejected signatures, and recovery.</p><p>Small mainnet transfers and wallet compatibility checks across the target platforms follow that testnet acceptance. Operational preparation includes an offsite backup and restore check and reviewing RPC capacity before wider availability.</p><p>Real screenshots and walkthroughs will accompany further development updates. Public release will follow transfer and platform acceptance.</p><p>We are building toward a straightforward experience: choose a network, review the costs, authorize the transfer, and follow native USDC into the account where it will be used. The current implementation makes that journey available for review while the next stage establishes the evidence for release.</p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4dd13183041e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scopuly for Mac Joins WalletConnect WalletGuide: Connect to Stellar dApps]]></title>
            <link>https://scopuly.medium.com/scopuly-for-mac-joins-walletconnect-walletguide-connect-to-stellar-dapps-3e396b88a87f?source=rss-bdf7585e89c7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e396b88a87f</guid>
            <category><![CDATA[stellar]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[walletconnect]]></category>
            <category><![CDATA[scopuly]]></category>
            <category><![CDATA[dapps]]></category>
            <dc:creator><![CDATA[Scopuly]]></dc:creator>
            <pubDate>Thu, 10 Sep 2026 21:07:42 GMT</pubDate>
            <atom:updated>2026-09-10T21:07:42.439Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0jFJ5zcvqPgPUEokLt6uMw.png" /><figcaption>Scopuly for Mac joins its WalletConnect WalletGuide listing, bringing Web, Desktop, and Mobile together.</figcaption></figure><h3>Connect to Stellar dApps from your browser, review transactions in your Mac wallet, and choose the connection method that fits your workflow.</h3><p>A typical DeFi session involves more than a single transaction. You explore an application, compare options, read the details, and decide what to do. Much of that happens in a browser.</p><p>The approval deserves just as much attention.</p><p>Scopuly for Mac brings wallet connections and transaction review into a dedicated desktop application, alongside the browser where you use Stellar dApps.</p><p>We have now reached another milestone: <strong>the WalletConnect team has approved the addition of our macOS application to Scopuly’s existing WalletGuide listing.</strong></p><p>The update is published. Scopuly now appears with <strong>Web, Desktop, and Mobile</strong> platforms.</p><p><a href="https://walletguide.walletconnect.network/?search=scopuly">View Scopuly on WalletConnect WalletGuide</a></p><h3>A Desktop Wallet for Your Stellar Workflow</h3><p>Scopuly is available from the Mac App Store, giving Stellar users a dedicated wallet on the same computer where they browse and interact with dApps.</p><p>You can keep a dApp open in your browser, receive its requests in Scopuly, review the transaction, and approve or reject it from the wallet.</p><p>The WalletGuide update adds Desktop to Scopuly’s published platform information in the WalletConnect ecosystem. How a connection appears still depends on the dApp: some offer a wallet selector and a direct link to launch Scopuly, while others provide a WalletConnect QR code with a copyable connection URI.</p><p>Scopuly for Mac supports both desktop deep links and manual URI pairing.</p><p>This milestone covers our WalletGuide listing update. WalletConnect Certified is a separate designation.</p><h3>Your First WalletConnect Connection on Mac</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N9_f8V8x70JTvcYOnPTeOg.png" /><figcaption>Connect Stellar dApps to Scopuly for Mac through WalletConnect - no browser extension required.</figcaption></figure><p>You do not need the Scopuly browser extension to connect through WalletConnect.</p><p>Here is the basic workflow:</p><ol><li><strong>Install Scopuly.</strong> Download the application from the Mac App Store, then create a wallet or import an existing one.</li><li><strong>Open a compatible Stellar dApp.</strong> Use your preferred browser and select its WalletConnect connection option.</li><li><strong>Connect to Scopuly.</strong> If the dApp offers a direct launch, allow it to open the wallet. Otherwise, copy the complete connection URI beginning with wc:.</li><li><strong>Pair in the wallet.</strong> Open <strong>More → dApps → Pair WalletConnect</strong>, paste the URI, and start pairing.</li><li><strong>Review the proposal.</strong> Check the dApp name, website address, requested network, permissions, and selected account before approving.</li></ol><p>Keep the dApp’s connection screen open while pairing completes.</p><p>Once approved, the dApp receives the selected public Stellar account, and the session appears in Scopuly’s connected dApps list.</p><p><strong>Approving a connection does not approve every future transaction.</strong> Signing requests require a separate review and decision.</p><p><a href="https://apps.apple.com/us/app/id1383402218?platform=mac">Download Scopuly for Mac</a></p><h3>What Happens When a dApp Requests a Signature?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F3gXd-gDU-r0uN6iA0ptlQ.png" /><figcaption>Review transaction details in your Mac wallet. Every signing request requires a separate decision.</figcaption></figure><p>Suppose you prepare an operation in a Stellar application and proceed to confirmation.</p><p>The dApp sends a request to Scopuly. The wallet presents the requesting application, network, source account, transaction operations, memo, and available warnings.</p><p>This is the point to check whether the request matches what you intended to do.</p><p>Scopuly’s WalletConnect integration supports two transaction methods:</p><ul><li><strong>stellar_signXDR</strong> signs the transaction and returns the signed XDR to the dApp without submitting it.</li><li><strong>stellar_signAndSubmitXDR</strong> signs the transaction and submits it to the selected Stellar network through the wallet.</li></ul><p>That distinction matters. A successful signature does not necessarily mean a transaction has reached the blockchain. With a sign-only request, the dApp handles the next step.</p><p>Scopuly supports <strong>Stellar Mainnet and Testnet</strong>. The wallet’s active network must match the signing request. If the networks differ, signing is blocked until the mismatch is resolved.</p><p>For developers testing an integration, Testnet provides a way to exercise the connection and transaction flow with test funds.</p><h3>Where the Scopuly Browser Extension Fits</h3><p>WalletConnect is one way to connect. Scopuly also offers a browser extension for applications that integrate the Scopuly provider.</p><p>The extension exposes window.scopuly to compatible Stellar dApps and communicates with a paired Scopuly wallet through <strong>Scopuly Bridge</strong>.</p><p>The paired wallet can be on your phone or your Mac.</p><p>The workflow is straightforward:</p><ol><li>Install the extension and pair it with Scopuly.</li><li>Open a compatible dApp and approve access to your selected public account.</li><li>Review signing requests and give final approval in the paired wallet.</li></ol><p><strong>Private keys and seed phrases do not enter the extension.</strong> The paired Scopuly application performs the signing operation.</p><p>This gives users a choice of where they want to review and approve requests. Someone working entirely on a Mac can use the desktop wallet. Someone who prefers approval on a separate device can use their paired mobile wallet.</p><p><a href="https://chromewebstore.google.com/detail/scopuly-stellar-mobile-si/gfblddiiepicpjpffokeojikcphggmmd">Get the Scopuly Browser Extension</a></p><h3>Which Connection Method Should You Use?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jcpKkGfoto7aemOsQDL08g.png" /><figcaption>Use the Scopuly extension with your Mac or mobile wallet. Your private keys stay in the paired wallet.</figcaption></figure><p>Start with the connection options offered by the dApp.</p><p>If it supports <strong>WalletConnect for Stellar</strong>, connect Scopuly through its WalletConnect flow. The browser extension is optional for that workflow.</p><p>If it integrates the <strong>Scopuly provider</strong>, use the extension with your paired wallet.</p><p>These are separate integrations. A website that supports one does not automatically support the other.</p><p>We also clarified the extension’s listing requirements with the WalletConnect team. Their recommendation is to keep Scopuly’s listing focused on its WalletConnect-enabled applications and mention the extension separately in the description.</p><p>The extension continues to use its own provider and bridge connection. It does not currently announce an EIP-6963 provider for direct browser detection by AppKit.</p><h3>Stay in Control of Your Connections</h3><p>A desktop wallet becomes useful when it makes everyday decisions easier to inspect.</p><p>On Mac, you can keep the dApp and wallet side by side, compare the requested operation with the action you prepared, and review the details before signing.</p><p>You can also manage your connections from Scopuly’s dApps section. When you finish using an application, disconnect its session. A later connection will require pairing again.</p><p>The new Desktop listing is another step toward making Scopuly available wherever Stellar users choose to work: on mobile, on the web, and on Mac.</p><p><strong>Try it with a Stellar dApp you already know. Connect your wallet, review a request, and experience the workflow on your desktop.</strong></p><p><a href="https://apps.apple.com/us/app/id1383402218?platform=mac">Download Scopuly for Mac</a> · <a href="https://walletguide.walletconnect.network/?search=scopuly">Explore Scopuly on WalletGuide</a> · <a href="https://scopuly.com/">Visit Scopuly</a></p><p>🔹 X: <a href="https://x.com/scopuly">x.com/scopuly</a><br>🔹 Telegram: <a href="https://t.me/scopuly">t.me/scopuly</a><br>🔹 YouTube: <a href="https://www.youtube.com/scopuly">youtube.com/scopuly</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e396b88a87f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>