106 releases 106 tags

RSS feed

• v1.0.0-beta.26 9ad3529127

  Compare

  Morphit v1.0.0-beta.26 Stable

  agorise released this 2026-06-22 23:33:03 +00:00 | 107 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A reliability release, with one fix that matters more than all the others: new
  account creation works again. On the way to launch we discovered that the Blurt
  library Morphit relies on couldn't sign the two operations behind account
  sign-ups and the relay's automatic token top-up, so a relay with plenty of funds
  could still turn people away with a misleading "temporarily out of funds"
  message. That's fixed. Alongside it: the "a new version is ready" prompt now
  appears on desktop, not just mobile; the node-health screen shows your
  account-creation-token buffer at a glance; the block explorer's account page got
  a thorough polish; and a handful of smaller display bugs are closed.

  For operators: morphit-ops upgrade handles this release the usual way — it runs
  npm ci and rebuilds the web frontend, the command-line tools, and the MCP
  server for you. Like the last few betas, this release changes no third-party
  dependencies, so there's no special install step beyond the upgrade tool. After
  upgrading, your relay will top its account-creation-token buffer back up on its
  own; you can watch it on the node-health screen (option 13 in morphit-ops).

  New

  • Node health shows the auto-minter. The node-health screen now reports your
    relay's automatic account-creation-token (ACT) minter right next to version and
    uptime: a green "✓ N ACT's ready" with the buffer it tops up to, or a red
    "Disabled" if you've turned it off. It's on by default for every instance, so a
    relay keeps itself stocked to create accounts without you having to think about
    it.
  • The block explorer shows an account's four public keys. The account page now
    lists Owner, Active, Posting, and Memo public keys, instead of just the posting
    key — the full picture for anyone inspecting an account on-chain.
  • Reachability addresses are clickable. On the public instances directory, an
    instance's Tor, Lokinet, I2P, and Nostr addresses are now links you can open
    directly, rather than text you had to copy out of a tooltip.

  Fixed

  • New account sign-ups work again — and the relay restocks itself. The two
    on-chain operations behind creating an account and minting account-creation
    tokens couldn't be signed by the bundled Blurt library, which is why some
    instances showed "our registration service is temporarily out of funds" even
    with a healthy balance. Both operations now sign correctly, so sign-ups go
    through and the relay refills its token buffer automatically.
  • The "update ready" prompt now appears on desktop. Previously the prompt to
    load a freshly deployed version reliably showed up on mobile but often never
    appeared on a desktop browser, which would quietly pick up the new version on
    its own. The desktop prompt now appears the way it should, so loading an update
    is your choice on every device.
  • The footer remembers your instance's name. An over-eager cache could revert
    the operator's instance name in the footer back to the default until a hard
    reload; it now stays correct after a normal page load.
  • The order book's interest rate reads correctly. A display bug overstated the
    live BLURT annual rate by roughly five times on one surface; it now matches the
    real, on-chain-derived figure (the rate is always computed live, never
    hard-coded).
  • "Load older operations" no longer stalls near the start of history. On the
    explorer's account page, paging further back used to silently fail once you got
    close to the beginning of an account's history; it now loads the remaining
    operations correctly, with a clear loading indicator.
  • Explorer account links resolve. Transaction and block links on the account
    page no longer lead to a not-found page.
  • Two smaller display bugs. A profile picture that could differ between
    surfaces now derives from one consistent source, and a private account card no
    longer briefly appears for signed-out visitors.

  Improved

  • An accurate voting-power reading. The account's voting-power percentage now
    accounts for delegation (power received and delegated away), so heavy delegators
    see a correct figure rather than an understated one. For an account with no
    delegation, nothing changes. The label across the app is now simply "Voting,"
    and the accompanying hint drops an old, inaccurate description of how the chain
    charges for actions.
  • Clearer wording while signing in and setting up keys. Several small pieces of
    on-screen text on the login, avatar, and key-import screens were reworded for
    clarity, the key-import field now caps overly long input, and a private-key field
    shows a clearer icon.
  • A friendlier "leave this page?" warning. The prompt shown if you try to
    navigate away while choosing a username is now plainer, and the page previews
    your chosen "@name" on the claim button as you type.

  Under the hood

  • More regression guards. New automated checks pin the behaviors above — the
    account-creation-token serializers (proven byte-for-byte against the reference
    library), the node-health auto-minter line, the desktop update prompt, and the
    cache rules that keep the update surface fresh — so a future change can't quietly
    undo them.
  • The full project test suite runs clean again. Two service components that
    carry their checks as standalone smoke tests rather than unit tests were causing
    the repo-wide npm test to report a false failure; the command is green end to
    end again.
  • A repo-wide audit pass. A full security and code audit — including hostile-
    input checks on every on-chain operation handler, a sweep for dead database
    fields, stale references, and resource leaks, and complete persona walkthroughs
    across the app, the operator tools, and the read-only agent interface — found the
    tree in good shape, with the fixes above applied.
  • Translation upkeep. Every new or reworded piece of on-screen text ships in
    all ten languages.

  Downloads

  • morphit-v1.0.0-beta.26.tar.gz
    3 downloads · 2026-06-23 01:07:31 +00:00 · 9.9 MiB
  • morphit-v1.0.0-beta.26.tar.gz.sha256
    5 downloads · 2026-06-23 01:07:28 +00:00 · 96 B
• v1.0.0-beta.25 61fc71d3c1

  Compare

  Morphit v1.0.0-beta.25 Stable

  agorise released this 2026-06-22 02:57:16 +00:00 | 109 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A trust, transparency, and launch-readiness release. The headline for operators
  is that the project's treasury addresses (BLURT, BTC, and XMR) are now baked into
  the software itself as a single source of truth — and the public instances
  directory flags any instance whose on-chain treasury doesn't match them, so a
  look-alike can't quietly redirect fees. Operators can also set their instance's
  display name and branding on the directory card. For everyone else: signing out
  now signs you out everywhere, the FAQ search is more precise, and a couple of
  small interface bugs are closed. Under the hood, the on-chain release machinery
  that the public launch depends on was completed and hardened.

  For operators: morphit-ops upgrade handles this release the usual way — it runs
  npm ci and rebuilds the web frontend, the command-line tools, and the MCP
  server for you. Like beta.24, this release changes no third-party
  dependencies, so there's no special install step beyond the upgrade tool.

  New

  • The project treasury is part of the software now. The canonical BLURT, BTC,
    and XMR treasury addresses are baked into the code as the single source of
    truth, rather than something each piece configures separately. Fee routing and
    every on-chain treasury check derive from that one place, which removes a whole
    class of "which address is right?" mistakes.
  • The directory flags treasury mismatches. On the public instances page, an
    instance whose on-chain treasury address doesn't match the canonical project
    treasury now carries a clear mismatch indicator — a trust signal that makes a
    fee-redirecting look-alike visible at a glance.
  • Name and brand your instance. Operators can set their instance's display
    name and branding for its directory card through morphit-ops, so your node
    shows up the way you want it to.

  Fixed

  • Sign out means sign out — everywhere. Signing out from any control,
    including the avatar menu, now clears your session across the whole app
    consistently, instead of leaving some surfaces still showing you as signed in.
  • Your instance's directory name actually updates. A bug kept an operator's
    chosen instance name from changing on the directory card; it now reflects what
    you set.
  • The asset picker on the order book closes properly. Selecting an asset no
    longer leaves the picker stuck open.

  Improved

  • Sharper FAQ search. Search now accepts ordinary straight quotes (not just
    curly ones) for exact-phrase matching, waits for a few characters before it
    starts matching so a single keystroke doesn't flood the results, and subtly
    highlights the matched terms so you can see why a result came up.
  • A foolproof path to the on-chain release. The release ceremony now has
    proper tooling: a laptop-only helper signs and broadcasts the on-chain release
    record with the signing key entered at a masked prompt (never stored, never
    logged), and previews exactly what it will send before asking for the key. The
    release bundle's integrity manifest now generates in the exact format the
    on-chain record and the in-browser verifier expect.
  • Clearer launch documentation. The operator launch runbook was de-duplicated
    and reconciled into one canonical sequence, so there's a single, unambiguous
    set of steps to follow at go-live.

  Under the hood

  • The on-chain release pipeline works end to end. The chain of build → integrity
    manifest → signed release record was completed and proven end to end, and is now
    pinned by automated checks so it can't drift back out of shape. This is the
    groundwork the public launch (which will let any visitor's browser verify the
    running site hasn't been tampered with) is built on.
  • Leaner chat bundle. A type-only import was corrected so a byte-handling
    polyfill no longer rides along into a chat code chunk it never needed.
  • More regression guards. New automated checks pin the behaviors above — the
    treasury single-source-of-truth, the release-manifest format, and more — so a
    future change can't quietly undo them.
  • Translation upkeep. Every new or reworded piece of on-screen text ships in
    all ten languages.

  Downloads

  • morphit-v1.0.0-beta.25.tar.gz
    3 downloads · 2026-06-22 03:37:41 +00:00 · 9.8 MiB
  • morphit-v1.0.0-beta.25.tar.gz.sha256
    4 downloads · 2026-06-22 03:37:34 +00:00 · 96 B
• v1.0.0-beta.24 be90400a42

  Compare

  Morphit v1.0.0-beta.24 Stable

  agorise released this 2026-06-21 05:15:04 +00:00 | 110 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A reliability, self-healing, and polish release. The headline for operators is
  that your instance now keeps its own account-creation buffer topped up by
  itself — so new sign-ups stop failing silently when that buffer runs dry — and
  it alerts you the moment account creation is actually being refused. For
  everyone else: a sign-in bug that wrongly rejected a valid account is fixed, a
  couple of subtle key- and order-handling issues are closed, the FAQ comparisons
  are refreshed, and a long tail of smaller annoyances is tidied up.

  For operators: morphit-ops upgrade handles this release the usual way — it runs
  npm ci and rebuilds the web frontend, the command-line tools, and the MCP
  server for you. Unlike beta.23, this release changes no third-party
  dependencies, so there's no special install step beyond what the upgrade tool
  already does. If you haven't already, this is a good moment to set your alert
  address (morphit-ops → Matrix alerts) so the new account-creation alerts
  actually reach you.

  New

  • Your instance keeps itself able to create accounts. Creating a new account
    consumes a pre-minted "account token" the relay holds in a small buffer; when
    that buffer empties, sign-ups fail — regardless of how much BLURT the relay is
    holding. The relay now refills that buffer on its own, in the background,
    spending only above a reserve you set, so you no longer have to top it up by
    hand. This is on by default; set the auto-mint switch to off if you'd rather
    manage it yourself.
  • An alert the moment sign-ups are actually being refused. Previously, if the
    account-creation buffer ran dry, new users just hit a failure and you got no
    warning (the only balance alert watched BLURT, which could be plentiful while
    the buffer was empty). There's now a CRITICAL alert that fires exactly when the
    buffer falls to the point where sign-ups are being rejected — and clears itself
    when it recovers — so a silent sign-up outage can't go unnoticed.
  • Exact-phrase FAQ search. Wrap a search in quotes ("…") to match that exact
    phrase instead of the individual words.

  Fixed

  • Sign-in no longer wrongly rejects a valid account. Importing or signing in
    could report a perfectly valid account as "invalid" because the account-lookup
    request was being built with a doubled slash in the URL that the server then
    refused. The address is now always built correctly, so a real account is found.
  • The right key, every time. On the key panel, the short fingerprint shown on
    screen could differ from the full key the Copy button actually gave you. It now
    shows a shortened form of the same value you copy.
  • No accidental duplicate orders. If you navigated away while an order was
    mid-broadcast — unsure whether it had landed — and then posted again, you could
    create a second, duplicate order on-chain (each attempt gets its own random
    identifier). Navigation is now held while an order is being broadcast, the same
    protection the account-creation step already had.
  • "Register when you're ready" actually points somewhere. A sign-up message
    used to tell people to "register from Settings," but Settings has no
    account-creation step — only on-chain name verification. The wording now points
    at the real path (the register prompt on the order book), in all ten languages.
  • Operator console fixes. The morphit-ops status dashboard no longer dead-ends
    with "No database URL configured" when you run it from outside the install
    directory, and the menu's colored markers (including the bright "update
    available" flag) render in color again.
  • Quieter console behind the beta gate. A harmless-but-noisy manifest 401
    during the beta's password gate is resolved.
  • Smaller fixes. Clicking the logo (and a couple of other spots) no longer
    drops your in-memory session; a fresh page no longer loads with its top heading
    tucked under the sticky header; and a "you're about to switch accounts" prompt
    prevents a stale-session mix-up on the sign-in page.

  Improved

  • The FAQ comparisons are current. The "how is Morphit different from …"
    articles were reorganized and brought up to date — including the recent
    real-world events that make the case (a major Bisq/Haveno-class exploit and the
    shutdown of a long-running competitor) — across all ten languages.
  • One wordmark, loaded once. The header, hero, and footer logo are now the
    exact same asset, fetched a single time and cached, instead of being requested
    repeatedly.
  • Glossary and copy. The glossary intro, the "BLURT Power" entry, and a number
    of labels and descriptions were tightened, with every change shipped in all ten
    languages.

  Under the hood

  • Self-healing by default. The account-token refill loop is bounded (it never
    spends below your reserve, mints only toward a target, and caps how much it does
    per cycle) and logs what it does, so the relay can keep itself healthy without
    surprising you.
  • More regression guards. New automated checks pin the behaviors above — the
    duplicate-order guard, the corrected sign-in lookup, a documentation-vs-code
    check that catches an operator example naming a setting the software doesn't
    read, and more — so a future change can't quietly undo them.
  • A deep, repo-wide audit pass. A multi-session review swept every workspace
    for drift, dead code, hostile-input handling, privacy leaks, and documentation
    accuracy; the findings it surfaced are the fixes above.
  • Translation upkeep. Every new or reworded piece of on-screen text ships in
    all ten languages.

  Downloads

  • morphit-v1.0.0-beta.24.tar.gz
    3 downloads · 2026-06-21 05:58:11 +00:00 · 9.3 MiB
  • morphit-v1.0.0-beta.24.tar.gz.sha256
    5 downloads · 2026-06-21 05:58:08 +00:00 · 96 B
• v1.0.0-beta.23 6ff183e4f4

  Compare

  Morphit v1.0.0-beta.23 Stable

  agorise released this 2026-06-20 05:00:08 +00:00 | 111 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A privacy, reliability, and polish release. The headline is that your browser
  no longer talks to third-party Blurt nodes to do everyday things: reading your
  balance and history, browsing the block explorer, and confirming your key when
  you sign in all now go through the instance you're already using. That closes a
  quiet leak where outside servers could see your IP address and which account you
  were looking at. On top of that, the "a new version is available" prompt now
  shows up reliably, the QR sign-in code lasts its full five minutes, signing in
  checks your input more helpfully, the first-trade flow is clearer, and a long
  list of smaller annoyances are fixed.

  For operators: this release does require reinstalling dependencies — run
  npm install (or npm ci) as part of your deploy, because a dependency was
  updated since beta.22. If you run behind BunkerWeb and your instance was first
  deployed before the frontend config was switched to a bind-mount, do a one-time
  docker compose up -d frontend so the new no-cache rules for the update files
  take effect (a plain restart won't attach the new volume; fresh installs get it
  automatically). morphit-ops upgrade now also rebuilds the command-line tools
  and the MCP server, not just the web frontend.

  New

  • Your browser stops phoning third-party servers to read the chain. Looking
    at your balance, your transaction history, and the block explorer used to make
    your browser contact outside Blurt nodes directly — which meant those nodes
    could see your IP address and which account you were viewing. All of that now
    goes through the instance you're already on, so there's nothing new for an
    outside server to learn about you. It's also more reliable: reads no longer
    break just because one particular set of public nodes is down.
  • Signing in no longer leaks which account is yours. When you sign in or
    import a key, Morphit checks that your key matches your on-chain account. That
    check used to go straight to a third-party node, tying your IP to your account
    at the moment you logged in. It now goes through your instance instead. Your
    secret key still never leaves your device — only your public account name is
    ever looked up.
  • A "refresh now" button on the block explorer. An account's explorer page
    updates on its own, but slows down its checks when the page sits idle, so a
    brand-new transaction could take up to a minute to appear. There's now a
    refresh button that pulls the latest straight away, plus a small note so you
    know roughly how fresh what you're seeing is.

  Fixed

  • The logo no longer logs you out. Clicking the Morphit logo (and a couple of
    other spots) used to drop your in-memory session. Those now keep you signed in,
    the same way the rest of the site's links already did.
  • The "new version available" prompt now actually appears. On some setups a
    caching layer could keep serving the old app, so the prompt to reload into a
    fresh version never showed. The app now also checks the deployed version
    directly and offers the update even in that case.
  • The QR sign-in code lasts the full five minutes it promises. Pairing a
    phone by QR code could quietly expire after about a minute on some setups. It
    now stays valid for the whole five minutes.
  • Smaller fixes: a couple of explorer/account links that showed a placeholder
    and led nowhere now work; a mistyped "blurt.media" link that used to slip
    through is now caught.

  Improved

  • Signing in checks your input as you type. The account-name box re-checks
    when you edit it and turns red with a clear marker if the name can't exist or
    isn't found; the posting-key box flags an obviously-wrong key the moment you
    paste it; the confirm-password field tells you right away if it doesn't match.
    A connection problem never shows a false red — that isn't your fault.
  • The "how will you pay?" step is clearer. The payment section on a new
    listing was relabeled and tidied, the four payment categories now start
    collapsed so the page isn't a wall of options, and the currency you want paid
    in is now a searchable picker instead of a free-text box.
  • Your first trade is guided. Because a brand-new account needs a little
    BLURT before it can do anything else, your very first trade is set up as a buy
    of BLURT — explained on the page, with the listing fee waived — and is set to
    expire in seven days. After that first trade, everything is fully open as
    before.
  • A few helpful notes added. The instances page suggests bookmarking a few
    instances (and their privacy-network addresses) since the order book lives
    on-chain and is reachable through any of them; the privacy page now spells out
    plainly what Morphit does and doesn't collect; and the "back up my keys" page
    shows the right guidance when you signed in with only a posting key.
  • Small polish. Your avatar matches your public profile everywhere, the cards
    on your Orders page lift on hover and press on click, rows with a checkbox or
    radio button highlight on hover, and a number of labels and bits of wording
    were tightened.

  Under the hood

  • Privacy-first by construction. The chain reads and the sign-in key check
    now run server-side on the instance you're using, over its own vetted set of
    nodes, so no outside party sees your IP or your account during normal use. The
    parts that exist specifically to catch a misbehaving instance — verifying
    signatures, release authenticity, and a chat correspondent's key — deliberately
    still query the wider network directly, because routing those through a single
    instance would defeat their purpose.
  • A dependency was updated to pick up upstream security fixes, which is why
    this release needs npm install on deploy.
  • More regression guards, and translation upkeep. New automated checks pin
    the behaviors above so a future change can't quietly undo them, and every new
    or reworded piece of on-screen text ships in all ten languages.

  Downloads

  • morphit-v1.0.0-beta.23.tar.gz
    3 downloads · 2026-06-20 05:40:08 +00:00 · 9.3 MiB
  • morphit-v1.0.0-beta.23.tar.gz.sha256
    4 downloads · 2026-06-20 05:40:06 +00:00 · 96 B
• v1.0.0-beta.22 b722356698

  Compare

  Morphit v1.0.0-beta.22 Stable

  agorise released this 2026-06-19 03:48:48 +00:00 | 112 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A sign-in, session, and polish release. The headline is that your session now
  follows you across browser tabs: open a Morphit link in a new tab — or reload
  one tab while others stay open — and you no longer have to sign in again, with no
  keys ever written to disk. And when you sign out, you now sign out of every open
  tab at once. On top of that, signing in got more helpful as you type, your avatar
  now matches your public profile everywhere, two broken account links are fixed,
  and a handful of smaller annoyances are cleaned up.

  For operators: there's nothing required beyond deploying this build. Everything
  in this release is on the visitor side — there are no configuration, service, or
  command changes since beta.21.

  New

  • Stay signed in across your open tabs. If you already have Morphit open and
    unlocked in one tab, opening a link in a new tab (or reloading another tab)
    picks up your session automatically — no second sign-in, not even a password
    prompt. Your keys are handed from tab to tab in memory only; they are never
    written to disk and they disappear the moment your last Morphit tab closes.
    This is separate from "Remember me," which remains the opt-in for surviving a
    full browser close.
  • Sign out everywhere at once. Signing out in one tab now also signs you out
    of every other open Morphit tab, so an explicit sign-out leaves no session
    lingering elsewhere. Closing a single tab, or letting a tab auto-lock after
    idling, does not sign out your other tabs — only an explicit Sign Out does.

  Fixed

  • Account links in the block explorer and your orders now work. A couple of
    links to an account's explorer page were showing a literal placeholder instead
    of the account name and led nowhere. Both now go to the right place.
  • No more phantom "Draft restored" message on a fresh New Post. Arriving at
    the New Post page from a prompt (for example the welcome flow, or a re-list)
    could later pop up a "draft restored" banner for a draft you never wrote.
    Pre-filled visits no longer save a stray draft, so the banner only appears for
    a draft you actually started.
  • "Back up my keys" handles posting-key sign-ins correctly. If you signed in
    with only a posting key, the page no longer offers a 12-word seed-phrase backup
    that doesn't apply to you; it shows the right note and keeps your encrypted
    keyfile backup.

  Improved

  • "Remember me on this device" now works however you sign in. Previously only
    a seed-phrase sign-in could be remembered; signing in with a JSON keyfile or a
    posting key is now offered the same choice. It stays unchecked by default, so
    nothing is saved to your device unless you ask for it.
  • Your avatar now matches your profile everywhere. The little identicon next
    to your name is now drawn from your account name consistently — so the avatar
    in the top-right menu matches the one on your public profile, in the order
    book, in chat, and everywhere else you appear.
  • The sign-in boxes check your input as you type. The account-name box
    re-checks whenever you edit it and turns red with a clear "invalid" marker if
    the name can't exist or isn't found on Blurt; the posting-key box flags an
    obviously-wrong key (wrong length or prefix) the moment you paste it. A
    connection problem never shows a false red — that isn't your fault.
  • Clearer wording in a few places. The welcome / first-trade card explains
    more plainly what your first trade gets you, and several labels and notes
    around saving links and keys were tightened. The "blurt.media" link box also
    now catches a mistyped address that used to slip through.
  • Small polish. The square cards on your Orders page lift on hover and press
    in on click like the rest of the site, and rows with a checkbox or radio button
    now show a subtle highlight when you hover them.

  Under the hood

  • Regression guards for the cross-tab session work. New automated checks pin
    the cross-tab sign-out so it propagates to sibling tabs, and — just as
    importantly — verify the safety rule that closing a tab or an idle auto-lock
    never signs you out of your other tabs. Closing this gap is what the release's
    cross-tab sign-out is about.
  • Regression guards for the sign-in validation. The new live checks on the
    account-name and posting-key boxes are pinned so a future edit can't quietly
    undo them.
  • Translation upkeep. Every new and reworded piece of on-screen text ships in
    all ten languages.

  Downloads

  • morphit-v1.0.0-beta.22.tar.gz
    10 downloads · 2026-06-19 04:30:39 +00:00 · 9.6 MiB
  • morphit-v1.0.0-beta.22.tar.gz.sha256
    8 downloads · 2026-06-19 04:30:37 +00:00 · 96 B
• v1.0.0-beta.21 5fc470ff13

  Compare

  Morphit v1.0.0-beta.21 Stable

  agorise released this 2026-06-18 02:54:50 +00:00 | 114 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A sign-in and account-setup release. The headline fix is that signing in with a
  Blurt posting key — and the final naming step of creating a brand-new account —
  now work in the browser; both were crashing on a low-level type mismatch that
  only showed up in the browser build, never in tests. On top of that, signing in
  got clearer end to end: you can sign in with a seed phrase, a JSON keyfile, or a
  posting key from one screen, the account-name box checks your name against Blurt
  as you type, and the error messages now tell you exactly what went wrong instead
  of a generic "import failed." New accounts now also receive all four of their
  Blurt keys, each copyable and downloadable, with a plain warning about never
  sharing them. A couple of smaller annoyances — the order book's filter menus not
  closing when you tapped away, and the FAQ search jumping the page when you
  pressed Enter — are fixed too.

  For operators: there's nothing required beyond deploying this build. Everything
  in this release is on the visitor side — there are no configuration, service, or
  command changes since beta.20.

  Fixed

  • Signing in with your posting key now works. Pasting a Blurt posting key to
    sign in was failing with a generic "import failed" message. The cause was a
    low-level type mismatch (a key was handed to the Blurt library as the wrong
    kind of byte array) that only surfaces in the browser, so automated tests
    never caught it. It's fixed, and the same fix also repairs the final
    name-registration step when creating a brand-new account, which was hitting the
    identical problem.
  • The order book's filter menus close when you tap away. Opening the Asset,
    Fiat, or Payment filter and then tapping somewhere else — including up in the
    page header — used to leave the menu stuck open. All three now close on an
    outside tap.
  • FAQ search no longer jumps the page when you press Enter. Typing a question
    and pressing Enter used to scroll the page to a seemingly random spot. Enter is
    now ignored in the FAQ search; you pick an answer from the suggestions list by
    tapping it.

  Improved

  • Sign in with a seed phrase, a JSON keyfile, or a posting key — from one
    screen. The sign-in screen now says exactly that, the "go back" link is a
    real link, and the wording around using a posting key is clearer about what it
    can and can't do (you can read, post, and trade, but changing your account keys
    still needs a wallet like blurtwallet.com).
  • The account-name box checks your name as you type. It strips a leading "@"
    for you, turns red if you type a character that can't be in a Blurt username,
    and — once you've typed a valid name — quietly confirms with a "looks good!"
    that the account actually exists on Blurt.
  • Much clearer sign-in errors. Instead of one generic failure message, the
    sign-in flow now tells you precisely what happened and highlights the field at
    fault: you pasted your master password instead of your posting key; you pasted
    the wrong kind of key (owner, active, or memo); the key is valid but belongs
    to a different account; the account name wasn't found; or the Blurt network
    couldn't be reached (which is a connection problem, not a problem with your
    key).
  • Pasting a seed phrase is more forgiving. If you paste a seed with commas
    between the words, or with capital letters, Morphit tidies it up for you when
    you click away from the box.

  New

  • New accounts now receive all four Blurt keys. When you create an account,
    you can reveal your owner, active, posting, and memo keys, each with a one-tap
    copy button and a "download as a text file" option. A prominent warning
    explains, in plain language, that anyone holding one of these private keys has
    full control of the account and its funds — so they should never be shared with
    Morphit, support, friends, or any website. (Morphit never uses a master
    password; these individual keys are what you keep.) The same panel is available
    later from the Back up my keys page.

  Under the hood

  • New key-handling helpers, each proven to match the Blurt library exactly.
    This release adds the ability to write out a private key in the standard Blurt
    WIF format, to recognise when someone has pasted a master password instead of a
    key (by comparing only public, on-chain information — never an oracle for any
    secret), and to derive the four-key backup set. Each is verified byte-for-byte
    against the reference Blurt library, both in-sandbox and by automated checks
    that run on every build, and none of this key material is ever logged, stored,
    or sent over the network.
  • Regression guards for the sign-in and order-book fixes. New automated
    checks pin the posting-key conversion, the master-password detection, the seed
    tidy-up, the four-key derivation, and the order book's tap-away-to-close
    behaviour, so a future edit can't quietly undo them.
  • Translation upkeep. Every new piece of on-screen text ships in all ten
    languages, and an unused leftover string was removed.

  Downloads

  • morphit-v1.0.0-beta.21.tar.gz
    6 downloads · 2026-06-18 03:36:59 +00:00 · 9.6 MiB
  • morphit-v1.0.0-beta.21.tar.gz.sha256
    9 downloads · 2026-06-18 03:36:57 +00:00 · 96 B
• v1.0.0-beta.20 8762c4bd4a

  Compare

  Morphit v1.0.0-beta.20 Stable

  agorise released this 2026-06-16 17:12:32 +00:00 | 116 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A reliability and polish release, with most of the new work aimed at operators.
  The optional Matrix alert bot is now something you set up and verify with two
  short commands instead of hand-editing systemd, and several bugs that quietly
  stopped it from starting on a fresh deploy are fixed. On the visitor side, the
  home page and order book start faster, the "new version available" banner now
  appears promptly when you come back to the tab, and a trade chat can offer a
  one-tap prompt to turn on reply notifications. A wrong description of the
  welcome bonus in the FAQ was corrected in every language.

  For operators: there's nothing required beyond deploying this build. If you want
  Matrix alerts, morphit-ops matrix set @you:your.server turns them on and
  morphit-ops matrix test sends you a real test alert so you know delivery works
  end to end. If you upgrade from beta.19 and had configured the alert bot, this
  build is the first one where its service unit actually starts cleanly.

  Improved

  • The home page and order book load faster. The browser no longer pulls the
    elliptic-curve signing and seed-phrase libraries (and the Blurt client) into
    the very first page load on pages that don't need them. First-paint JavaScript
    on the home page dropped by roughly a fifth. These libraries still load the
    moment you do something that needs them — create an account, sign in, open an
    encrypted chat — and not before.
  • The "a new version is available" banner now appears promptly. It used to
    rely on a slow background timer, so on mobile it could take several minutes to
    notice a freshly deployed build (and on a desktop tab that was already up to
    date it correctly showed nothing). It now re-checks the instant you bring the
    tab back to the foreground, or when your connection comes back, so the prompt
    shows up within a beat of an update being available.
  • Optional reply notifications inside a trade chat. When you open a trade
    conversation, Morphit can offer a small, dismissible prompt to turn on chat
    notifications so you're pinged when the other person replies even with the tab
    closed. It rides the same private web-push mechanism the rest of the app uses
    — an opaque browser endpoint, no email, phone number, or other personal detail
    — and "Not now" hides it for good.

  For operators

  • Manage the Matrix alert bot with morphit-ops matrix. The alert bot is
    installed by default but only runs once you give it a valid Matrix username to
    notify. morphit-ops matrix set @you:your.server turns it on (and starts it),
    morphit-ops matrix clear turns it off (and stops it), and morphit-ops matrix
    shows its current status. Upgrades re-check the setting automatically, so the
    bot's running state always matches your configuration.
  • Confirm alerts actually reach you with morphit-ops matrix test. One
    command asks the running bot to send you a clearly-labelled test alert DM, so
    you can verify the whole delivery path — token, direct message, encryption —
    without the old manual log-watching dance. (The first message from the bot
    arrives as a room invite you accept once.)
  • The alert bot's service unit now starts cleanly on a fresh deploy. Three
    packaging bugs that could stop the unit from starting — a mount path it never
    used, the wrong launcher path, and an over-restrictive /proc setting that
    broke its log reader — are fixed.
  • Alerts from the shell-based system monitors now reliably reach the bot. On
    some hosts, alerts emitted by the host/disk/firewall/etc. monitors were landing
    in the journal without the unit attribution the bot filters on, so the bot
    silently missed them. They now flow through the path that carries reliable
    attribution. (If your indexer and relay are your only alert sources, you were
    unaffected either way.)

  Fixed

  • The FAQ described the welcome bonus incorrectly. One FAQ answer said new
    traders receive "10 BP delegated"; the welcome bonus is actually 10 Blurt plus
    10 Blurt Power granted (powered up and owned, not a revocable delegation),
    and it omitted the liquid Blurt entirely. This was corrected in all ten
    languages, and a related reward-description wording fix was made in the two
    Chinese locales. The fee and reward reference docs were brought into line.

  Under the hood

  • A slimmed production install can no longer break the services at launch.
    The indexer, relay, Matrix bot, and MCP server all run their TypeScript source
    through tsx at runtime, but several of them only declared tsx as a dev
    dependency — so a production-style install (npm install --omit=dev,
    NODE_ENV=production) would have stripped it and stopped those services from
    starting. tsx is now a regular dependency wherever a service runs it, and a
    new check fails the build if that ever regresses.
  • The /dev diagnostic pages are disabled in production builds. The internal
    diagnostic pages (icon catalogue, responsive-layout preview, and a hardware
    security-key probe) were reachable on a deployed site. They now return "not
    found" in a production build and are available only when running the app
    locally for development.
  • DNS-rebinding hardening on the alert bot's local self-test endpoint, plus
    a small set of audit-driven accuracy fixes across the documentation.
  • Dependency-licensing transparency. A THIRD-PARTY-LICENSES.md now documents
    that the dependency tree is otherwise fully permissive except for one
    source-available (no-military-use) runtime library, and a new check fails the
    build if any non-free dependency license is introduced.

  Downloads

  • morphit-v1.0.0-beta.20.tar.gz
    4 downloads · 2026-06-16 19:43:05 +00:00 · 9.5 MiB
  • morphit-v1.0.0-beta.20.tar.gz.sha256
    5 downloads · 2026-06-16 19:43:03 +00:00 · 96 B
• v1.0.0-beta.19 b71c288012

  Compare

  Morphit v1.0.0-beta.19 Stable

  agorise released this 2026-06-15 19:40:09 +00:00 | 117 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A performance, privacy, and polish release. The biggest change is invisible: the
  app no longer loads its ~1 MB cryptography library until you actually need it —
  creating an account, signing in, or opening an encrypted chat — so first visits
  to the home page, the order book, and trader profiles are now markedly lighter.
  The app also stops quietly pinging every Blurt node the moment it loads, and it
  now talks directly only to the Blurt nodes that work correctly in a browser —
  both make the site quieter on the network and steadier in use. On top of that:
  primary buttons across the site now share one brand color, the onboarding wizard
  opens each step at the top, and the "a new version is available" banner no longer
  reappears in a loop.

  For operators: there's nothing to do beyond deploying this build. The browser's
  default direct-to-Blurt node list narrowed to the three nodes that serve correct
  CORS headers, but all six remain in your server-side config and CSP, so failover
  is unchanged.

  Improved

  • Pages load faster — the cryptography library is now fetched only when it's
    used. Morphit's signing/encryption library (libsodium) is about a megabyte,
    and it was being pulled into the very first page load on every page,
    including ones that never touch your keys (the home page, the order book, a
    trader's profile). It now loads the first time you actually do something
    cryptographic — create an account, sign in, open an encrypted chat, import a
    key — and not before. If you're just browsing offers, that megabyte never
    downloads. Nothing about the security changes: the same library does the same
    work the moment a key is involved; it simply isn't fetched until then.
  • The app no longer probes every Blurt node the moment it opens. Previously,
    opening the site kicked off background "are you alive?" requests to every
    Blurt RPC node in the pool, so the mere act of loading a page produced a
    fan-out of connections before you'd done anything. The client now reaches a
    node only when it has a real request to make, and learns which nodes are
    fastest from real traffic. Less noise on the network, and a smaller footprint
    for simply visiting.
  • Steadier direct connections to Blurt. The set of Blurt nodes the browser
    talks to directly is now limited to the three that return correct
    cross-origin (CORS) headers, so the browser no longer spends attempts on nodes
    it can't actually read from. The full set of nodes still backs the indexer and
    relay on the server side (where CORS doesn't apply), so there's no loss of
    redundancy — this only stops the browser from trying nodes a browser can't use
    anyway.
  • One consistent button color across the whole site. Primary action buttons
    — the header Start button and every filled call-to-action — now use a single
    deepened brand teal (chosen so white text clears the WCAG AA contrast bar)
    instead of a mix of greens, so the interface reads as one coherent set.

  Fixed

  • The "a new version is available" banner no longer loops. The small banner
    that appears when a new build has been deployed could, in some navigation
    patterns, re-fire repeatedly — popping back up after you'd dismissed it. It now
    attaches its update listeners once per service-worker registration and reloads
    at most once, so it shows up a single time and stays gone after you dismiss it.
  • The onboarding wizard now opens each step at the top. When the
    create-account flow advanced from one step to the next, it could leave you
    scrolled partway down the previous step. Each step now jumps to its own
    heading, so you always start reading from the top.

  Under the hood

  • libsodium now sits behind a lazy accessor ($lib/crypto/sodium): a single
    module-level sodium binding populated by a dynamic
    import('libsodium-wrappers-sumo') the first time ensureSodium() is awaited.
    Every async crypto entry point (keygen, keystore, WIF import, desktop pairing,
    backup codes, YubiKey wrap) awaits it first; the handful of synchronous
    sodium.* uses are all on paths that can only run after an async load has
    already happened. A new libsodium-not-in-baseline-closure-smoke asserts the
    ~1 MB chunk stays out of the every-page module-preload closure, and the chat
    crypto is reached via a dynamic import('$lib/chat/crypto') in the trade event
    listener so it never anchors into the baseline either.
  • The endpoint rotator no longer calls warmup() eagerly on construction. The
    method remains available for explicit opt-in, but the default path probes
    endpoints only on real demand, and the in-app endpoint list
    (EndpointList.svelte) wires deliberate probing only where a human is actually
    looking at node health.
  • The frontend default Blurt RPC pool (config.ts DEFAULT_RPC_ENDPOINTS) is
    now a curated subset — the three browser-CORS-clean nodes
    (rpc.drakernoise.com, rpc.blurt.blog, blurt-rpc.saboin.com). The full
    six-node canonical set still lives in @morphit/operator-config
DEFAULT_BLURT_RPC_ENDPOINTS (indexer + relay), both env examples, and the
    four-surface CSP connect-src. rpc-endpoint-canon-smoke now checks the
    frontend list is a non-empty subset (no stray nodes, at least two for
    failover, all HTTPS) while still pinning the server-side env examples to the
    full set.
  • Dependency-audit review: the npm audit gate gained documented allowlist
    entries for three dev-only advisories nested under vite (a dev-server
    path-traversal and two Windows-specific issues in vite/launch-editor) and
    the form-data CRLF advisory reached only through the matrix-bot's transitive
    request dependency. None reach production — operators serve prebuilt static
    assets with no Vite dev server running, and the matrix-bot makes only outbound,
    operator-configured homeserver calls with field names it constructs itself. No
    npm audit fix, no lockfile rewrite; the lockfile stays the tested source of
    truth.
  • The press/media kit (morphit-mediakit.zip) was regenerated for the new brand
    color (the palette grew from six entries to seven), with the build script's
    palette guard and the README color-standards table updated to match.

  Downloads

  • morphit-v1.0.0-beta.19.tar.gz
    4 downloads · 2026-06-15 20:20:40 +00:00 · 9.4 MiB
  • morphit-v1.0.0-beta.19.tar.gz.sha256
    9 downloads · 2026-06-15 20:20:39 +00:00 · 96 B
• v1.0.0-beta.18 9af0b3f55a

  Compare

  Morphit v1.0.0-beta.18 Stable

  agorise released this 2026-06-15 04:53:58 +00:00 | 118 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A small operator-quality release, plus one user-facing fix. For users: the
  printable backup card on the onboarding screen now renders instead of producing
  a blank page. For operators: it removes a recurring upgrade nag and makes the
  upgrade's "is the new build actually live?" check reliable — both changes are in
  morphit-ops upgrade itself, with nothing extra to do beyond deploying it. This
  release also expands the default Blurt RPC pool to six independent nodes and
  makes the client back off properly from rate-limited endpoints, so chain reads
  and broadcasts are steadier.

  Fixed

  • The printable backup card no longer prints as a blank page. On the
    onboarding "your keys are ready" screen, the Print backup card button could
    open the print/PDF dialog showing a single empty page. The card was isolated
    for printing using a position: fixed element inside a deliberately
    collapsed page subtree — a combination some print-to-PDF engines drop
    entirely. The card is now lifted to the top of the page and printed in normal
    flow, so it renders reliably as a single clean page. (The seed words still
    never leave your device — this is pure local rendering, no network, no PDF
    library.)
  • morphit-ops upgrade now tidies up old backups for you. Each upgrade
    keeps a rotating set of /opt/morphit.bak-<timestamp> backups and prunes
    the oldest. Previously, if you happened to have a leftover login shell, or a
    pager left open from a systemctl status …, parked inside one of those old
    backup directories, the upgrade refused to delete it and printed a [WARN]
    asking you to go find and stop those processes — on every single upgrade.
    The upgrade now prunes those backups anyway, because a parked shell or pager
    is harmless (the system keeps it running fine even though its working
    directory is gone). It still refuses to delete a backup only when something
    is genuinely running its code from it — for example, a relay or indexer you
    started by hand from the old tree — since deleting that out from under a live
    service would be unsafe.
  • The post-upgrade "is the new frontend live?" check is now reliable. That
    check, and the manual command it printed when it couldn't confirm
    automatically, used to grep a token out of the service worker — but that
    token is assembled at runtime and doesn't survive minification, so the check
    almost always came back "could not auto-verify" and the suggested
    curl … | grep -o 'morphit-[0-9]*' command returned nothing useful. It now
    reads the morphit_version field from /verify.json instead, which is a
    single, stable value. If you ever need to confirm the served version by hand,
    the upgrade now tells you to run curl -s <your-site>/verify.json and check
    that its "morphit_version" matches the build.
  • Two more Blurt RPC endpoints in the default pool, and rate-limited nodes
    now back off properly. The default Blurt RPC set grew from four to six
    independent public nodes (added rpc.drakernoise.com and
    blurtrpc.dagobert.uk), giving more headroom when an endpoint is slow or
    down. Separately, when a node replies 429 Too Many Requests, the client now
    parks it on a dedicated, longer cool-off (starting at 30 s and escalating)
    rather than re-trying it every couple of seconds — which was what kept
    re-triggering the rate limit. While a node is parked, requests are served
    from the other endpoints, so this is invisible in the UI; it just removes the
    needless 429 round-trips. Operators running a hand-written reverse proxy or
    CSP: if your deployment pins a connect-src allow-list, add the two new
    origins (https://rpc.drakernoise.com https://blurtrpc.dagobert.uk) to it
    and to your indexer/relay RPC env vars, or the browser/server will refuse to
    reach them. A fresh install picks all six up automatically.
  • A clearer error when the database URL was never expanded. If a
    MORPHIT_*_DATABASE_URL was set to a value containing a shell command
    substitution — e.g. a host written as $(docker inspect … ) — environment
    files are read literally (the shell never runs), so the substitution was
    passed through verbatim and morphit-ops failed with a baffling
    getaddrinfo ENOTFOUND $(docker inspect … ). The CLI now detects the
    unexpanded $(…)/backticks up front and tells you exactly what happened and
    how to fix it (resolve the host to a concrete IP, or publish the DB on
    localhost), instead of a cryptic DNS error.

  Under the hood

  • The backup-prune safeguard previously keyed on whether any process had its
    current working directory under the backup tree. That is a weak signal —
    it caught harmless campers (shells, less/pager processes) and blocked the
    prune forever. The new pidsRunningFrom check instead looks at whether a
    process's executable (/proc/<pid>/exe) or an absolute path in its command
    line lives under the tree, which is the real "unsafe to delete" condition;
    a process that merely parked its cwd there no longer blocks pruning. A new
    regression smoke (upgrade-backup-prune) pins this so the prune cannot
    silently revert to the cwd-blocks-forever behaviour.
  • The frontend freshness verification (readBuiltVersion /
    resolveServedVersion) now parses build/verify.json's morphit_version on both
    the built side and the served side, replacing the brittle service-worker
    token grep. The upgrade-frontend-deploy smoke was updated to cover the new
    parseVerifyJsonVersion parser.
  • The RPC pool gained a dedicated rate-limit cooldown ladder
    (DEFAULT_RATE_LIMIT_COOLDOWN_LADDER_MS, 30 s → 5 min) and an
    isRateLimitError predicate; a 429 now selects that longer ladder while
    any other transport failure stays on the generic one. The single source of
    truth for the default endpoint set (@morphit/operator-config
DEFAULT_BLURT_RPC_ENDPOINTS) carries the two new nodes, and the
    non-importing copies (frontend config.ts, the two env examples, the
    four-surface CSP connect-src) are kept in sync by rpc-endpoint-canon and
    csp-header-consistency. New rpc-pool-smoke scenarios cover the rate-limit
    ladder and the predicate.
  • morphit-ops' database-URL reader (readDatabaseUrl) now rejects an
    unexpanded shell command substitution ($(…) / backticks) with an actionable
    message before pg is ever handed the literal host; pinned by a new
    instance-env-loader-smoke scenario.

  Downloads

  • morphit-v1.0.0-beta.18.tar.gz
    4 downloads · 2026-06-15 05:35:18 +00:00 · 9.4 MiB
  • morphit-v1.0.0-beta.18.tar.gz.sha256
    6 downloads · 2026-06-15 05:35:16 +00:00 · 96 B
• v1.0.0-beta.17 7dc88bc1e0

  Compare

  Morphit v1.0.0-beta.17 Stable

  agorise released this 2026-06-14 19:43:03 +00:00 | 119 commits to main since this release

  Signed by agorise

  GPG key ID: 53524E1F1017EB9C

  A focused follow-up to beta16: it fixes a layout regression in the orderbook
  filters and makes the in-app update prompt more reliable. Everyone gets the
  fixes; there is nothing for operators to do beyond deploying it.

  Fixed

  • The orderbook filters no longer overlap each other. On narrow screens
    (most visibly on phones), opening one filter could leave a second filter
    painted on top of the open list — for example, the payment-method pills
    appeared in the middle of the open currency list, and the controls looked
    tangled together. Each filter now lifts cleanly above the others while it
    is open and the idle filters sit behind the active one's backdrop, so only
    one list shows at a time and tapping elsewhere closes it. This was a
    display-only regression introduced in beta16; if you saw it, simply
    loading this build fixes it (no cache clearing or reset needed once the
    new build is served).
  • The "A Morphit update is available" prompt is more reliable. "Load it
    now" now always applies the update — if the new version can't take over on
    its own within a moment (which can happen right after a hard refresh), the
    page reloads to pick it up instead of the button appearing to do nothing.
    A stale prompt also no longer lingers after an update has already been
    applied. (If your browser still shows a stuck prompt from before this
    build, clearing the site's data once clears it.)

  Under the hood

  • The three orderbook selects (asset, currency, payment method) are stacked
    on one page; each is its own stacking context, and at an equal z-index
    sibling contexts paint in DOM order, so an open dropdown was being painted
    under the filters that follow it. The fix makes each select's z-index
    conditional on its open state — elevated above the shared backdrop while
    open, dropped below it while closed — which both layers the open list
    correctly and lets a tap on an idle filter close the open one.
  • A regression smoke (orderbook-select-stacking) pins this layering across
    all three components so a future edit cannot silently fall back to the flat
    z-index that caused the overlap.
  • The update banner now clears its reference to a waiting service worker once
    there is nothing left to apply (so it can't show a dead prompt), and "Load
    it now" has a short fallback reload guarded against a double reload, for the
    cases where the controllerchange event never fires (an uncontrolled page
    after a hard refresh, or a wedged worker). Two new scenarios in
    service-worker-single-registration pin both behaviours.

  Downloads

  • morphit-v1.0.0-beta.17.tar.gz
    3 downloads · 2026-06-14 20:23:45 +00:00 · 9.4 MiB
  • morphit-v1.0.0-beta.17.tar.gz.sha256
    6 downloads · 2026-06-14 20:23:43 +00:00 · 96 B