-
Morphit v1.8.12
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 45smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 38smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 40smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 14smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 28m30smorphit-release / Build + publish release tarball (push) Successful in 29m6sreleased this
2026-07-23 22:01:15 +00:00 | 29 commits to main since this releaseNames and pictures show up when they should
Display names and avatars were sometimes missing — a row would show the default heart icon instead of someone's photo, and refreshing the page fixed it. That shouldn't have been necessary, and now it isn't.
When Morphit asks the server who someone is, two different answers can come back empty: "this person has no picture" and "the request failed." Morphit already told those apart, and deliberately remembered a failure for only a few seconds so it could try again shortly. The catch was that nothing ever did try again — pages only ask once when they load. So the short memory expired into silence and the row kept its placeholder until you navigated away.
Pages now ask again after a failed attempt, and only after a failed one. Someone who genuinely has no picture still settles on their icon straight away, without pointless retries.
A trader's reputation can be restored again
If Morphit's self-dealing checks flag two accounts, their reviews stop counting toward each other's score. That's deliberate. But of the four checks that can do this, only two were ever shown to the person running the node — and only those two could be undone.
The other two were invisible and permanent. A false positive suppressed a reputation forever: you couldn't see which check had fired, deleting the record by hand didn't help because the detector simply recreated it, and the database itself refused to record the decision. Every part of the system agreed on the same blind spot.
All four checks are now visible, clearable, and stay cleared. As with the existing behaviour-based check, clearing forgives what's already happened without going blind to what happens next — if the pattern genuinely resumes, it's caught again.
Reviews that don't count now say so
A profile could show reviews that quietly contributed nothing to the score, with nothing on screen explaining why. Two causes: reviews from an account flagged by one particular check weren't marked, and reviews not linked to any order weren't either.
Keeping both out of the score is correct — a review tied to no trade can't be checked against anything, and counting it would let anyone inflate their own reputation. The problem was the silence. Such reviews are now marked, so what you see and what the score says finally agree.
Contacting a trader
The Message button was hidden from anyone not signed in — so a visitor browsing the orderbook saw plenty of offers and no way to start. Clicking it now takes you to sign-in and returns you straight to that conversation. It's still hidden on your own orders, since you can't message yourself.
More of your post reward arrives as liquid BLURT
When Morphit publishes on your behalf, it now asks the blockchain to pay your share as liquid BLURT rather than the default mix of liquid and Blurt Power. The request is sent separately from the post itself, so if the chain ever declines it your post is completely unaffected — it simply pays out the usual way.
Nothing goes to the Morphit community from these posts. It never did, and that hasn't changed.
Fixes
- Importing an old key now confirms which account it recognised. If Morphit works out your account from the key alone, it says so instead of leaving the screen looking stalled with no username field and no explanation.
- Two settings cards had their heading and privacy label overlapping into unreadable text.
- A profile's headline number is now labelled when it's showing a plain average rather than the full score, so two profiles are never quietly measuring different things.
For people running a node
One database change, applied automatically on upgrade: the table recording moderation decisions now accepts all four self-dealing checks rather than two. Fresh installations get the same thing.
If you've been unable to restore someone's reputation despite clearing their flags, this is why — and
morphit-ops moderationwill now show you what was previously hidden. It also warns when flags exist outside the window you're looking at, since suppression itself has no time limit.Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.11
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 46smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 36smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 39smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 15smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 28m18smorphit-release / Build + publish release tarball (push) Successful in 29m10sreleased this
2026-07-23 07:18:13 +00:00 | 30 commits to main since this releaseThis release is almost entirely about one thing: signing out of one account and into another now actually gives you a clean slate. Several separate faults all pointed the same way, and together they meant a second account on the same browser could inherit the first one's settings.
Your settings no longer follow the wrong person
Sign out of one account, sign into another, open Settings — and you could be looking at the previous account's values. There were two causes, and both are fixed.
Sign out kept too much. It cleared your keys, your paired-device marker and your account name, and stopped there. Your display name, bio, links, chat peers, pinned conversations, unsent drafts and preferences all stayed behind. Most were stored per-account so the next person couldn't read them, but not all: your currency and region were kept under a single shared key, so they carried over outright.
Sign out now forgets everything that belongs to you and keeps only what belongs to this browser — your language, your auto-lock timing, your chosen nodes. It's built as a list of what to keep rather than a list of what to clear, so anything added later is forgotten by default instead of surviving until someone remembers it.
And the Settings page could look up the wrong account. It worked out which account's drafts to show once, when the page first opened. Sign out and back in without reloading and that answer was never revised, so the page kept reading the previous account's. It now re-checks whenever you sign in or out.
Settings that belong to you now follow you
Morphit already backed up your notification preferences, hidden accounts, privacy toggles and currency/region to the chain, encrypted so the operator only ever stores an opaque blob. But restoring only ever applied what it found — so an account that had never saved any settings restored nothing, and simply kept whatever the previous account had left behind.
Settings now reset to their defaults before your own are applied. "Nothing saved yet" means factory defaults, never "inherit the last person". Your syndication choices have joined the backup too, so they follow you to a new browser like everything else — and, like the other publishing options, they start switched off for a new account rather than inheriting a choice you never made.
You can now see what's public and what isn't
The Settings page writes to two different places and never said which was which. Your display name, avatar, bio and links go to a public, permanent record on the blockchain that anyone can read — that's the point, it's how a trading partner recognises you. Your notification settings, hidden accounts and region go somewhere else entirely, encrypted before they leave your device.
Every section now says which it is, in plain words, before you press anything.
Fixes
- The header button now always matches your state. Locking shows "Unlock"; signing out shows "Start". Signing out while already locked used to leave it stuck on "Unlock".
- Your avatar shows up straight away. After signing in on a new browser, the menu could sit on a placeholder while your profile page showed your real picture on the same screen — and then correct itself minutes later. Morphit was treating "not published yet" as "there is no picture"; publishing takes about a minute to become visible, so it now waits and checks again. Removing your avatar still takes effect instantly.
- Signing out no longer leaves your picture in other tabs. The tab you signed out from cleared it; the others didn't.
- Your public key shows on every order card. It was appearing on the order page but not always on the card, depending on whether a background job had caught up yet. All three places that show it now agree. The key is what proves an account is really yours, so "usually visible" wasn't good enough.
- Reviews that don't count now say so. A profile could state "this user has not been reviewed by any counterparty" directly above visible reviews. If every review is excluded from the score, the page now explains that instead of denying they exist.
For people running a node
Nothing to do. No database changes, no configuration changes, and nothing about how your instance runs is affected — this release is entirely browser-side.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.10
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 43smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 36smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 37smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 14smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 26m56smorphit-release / Build + publish release tarball (push) Successful in 27m51sreleased this
2026-07-23 01:57:24 +00:00 | 31 commits to main since this releaseProfiles now show the right person
Opening one profile and then another showed you the first person's reputation and reviews on the second person's page. Reloading fixed it, which is why it looked like a caching quirk — it wasn't. Moving between two profiles reuses the same page, and the page only ever fetched its data once, when it first opened. Everything after that was stale: reputation, ratings, reviews, live orders.
Profiles now reload whenever you move to a different one, and the old person's details are cleared before the new ones arrive, so there is never a moment where you are looking at a mix of the two.
One reputation number, not two
The same trader could show 4.75 on their profile and 3.97 on their order card. Both numbers were correct, but they were measuring different things, and only one of them was ever explained.
The number on order cards and in chat is a considered score: it starts cautious and rises as good trades accumulate, so a newcomer with three glowing reviews can't look like a veteran. The profile was showing the plain average instead — which always flattered, on the one page a person visits to decide whether to trust someone.
Profiles now lead with the same score you see everywhere else, with the plain average shown underneath and labelled, since that's what the star breakdown beneath it counts.
Old accounts can post again
If your Blurt account dates back to Steem and you've never changed your posting key, Morphit would let you sign in and then refuse everything you tried to do — setting a display name, uploading an avatar — insisting your key "doesn't control any account on the blockchain". It does, and other Blurt sites accept it happily.
Morphit asks the chain which account a key belongs to. For accounts of that vintage the chain's index simply has no record, and Morphit treated "no record" as "no such account". It now falls back to the account name you gave when signing in, and then checks that name against your account's real published keys before anything is broadcast. Nothing is trusted that wasn't verified; the check that matters is now the one being used.
Avatar size warnings that make sense
Three things were wrong here, all from the same cause: the upload screen was checking against limits that didn't match the real ones.
- A 3.5 KB image was reported as over a "3.0 KB maximum". The actual limit is 6 KB — it was never too big.
- A 2.9 KB image got a red error saying it was near the limit. It was less than half way.
- A file that genuinely was too large would have been told, reassuringly, that it was "getting close".
The screen now uses the real limits, and says three different things depending on which is true: nothing at all when you're fine, a gentle amber note as you approach 6 KB, and a clear red message — naming the actual maximum — if you go over. The text beside the picture no longer squashes into a narrow ribbon.
You can use your own name
If you sign in as @agorise or @kencode, you can now write that in your display name. Those names are protected so strangers can't pose as them, but the protection was catching the actual owners: you could set exactly
agoriseand nothing else — notAgorisewith a capital, not@agorise, notKen @ Agorise.Signing in proves who you are, so the account that holds a protected name is now free to use it. Everyone else is still blocked, including lookalikes built from Cyrillic or accented characters. Your short bio was never restricted.
Smaller touches
- The Send button stops shouting. Before you've typed anything, and while a message is sending, it's disabled — but it was rendering bright white and reading as the main thing to press. It now matches the message box beside it.
- More of the subject line fits. The "RE:" line under a chat header was cut short with obvious empty space to its right; the ⋮ menu was reserving room across all three lines. The subject now uses the full width.
- Quieter artwork. The large icons on the three settings cards are now grey and much fainter.
For people running a node
A failed backup is no longer kept as if it worked. This is the second half of the backup problem from v1.8.9, and it is worth reading if you run a node.
If your database was unreachable when the nightly backup fired, the script still wrote a small file, gave it a proper backup name, reported success, and exited cleanly. The health check then reported it as a fresh backup — because it genuinely was the newest file. A directory that looked like months of backups could have been months of 20-byte fragments.
The cause is that the standard shell on Debian and Ubuntu doesn't support the option that reports a failure in the middle of a chain of commands, so the script only ever saw the last step succeed. It now checks whether the database dump itself succeeded, and refuses to keep anything that failed or came back empty.
morphit-ops healthadditionally refuses to call an implausibly small dump fresh.What to do once, after upgrading:
sudo install -m 755 /opt/morphit/ops/backup/morphit-backup.sh /usr/local/lib/morphit/ ls -lS /home/morphit/backups | tail -20The first command installs the corrected script —
morphit-ops upgradedoes not replace it. The second lists your backups smallest-last: anything measured in bytes rather than kilobytes is a failed run from before this release, and should be deleted so it can't be mistaken for something you could restore from. A real dump is tens of kilobytes at minimum.You may now see backup failures reported where you previously saw silence. Those runs were already failing; you were simply not being told.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.9
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 46smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 38smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 41smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 14smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 28m11smorphit-release / Build + publish release tarball (push) Successful in 29m16sreleased this
2026-07-22 20:53:51 +00:00 | 32 commits to main since this releaseNo more pop-ups from the person you're already talking to
This is the third release in a row that has claimed to fix this, so here is what was actually wrong.
The code that stops a notification firing while you have that conversation open lives in the service worker — the small background program your browser keeps for Morphit. A service worker is the one part of a website that does not update when you reload the page: a new one installs and then waits, while the old one keeps running. Both previous fixes were correct and neither was ever running.
So the page itself now takes down any notification for the conversation you're looking at. Page code is fresh every time you load it, so this works no matter how old the background worker is. Messages from anyone else still notify exactly as before.
The subject line appears with the message
A new conversation used to arrive in your inbox within seconds, but its subject sat as a placeholder for about a minute. Morphit now looks up the listing straight away, so the card arrives complete. Conversations that aren't about a listing no longer show a placeholder that was never going to fill in.
Clearer order titles
An order with no minimum or maximum used to be titled just "I'm buying BLURT" — the vaguest listing got the least helpful title, exactly when a reader most needs to know what you'd pay with. Titles now always say what you're trading and in which currency:
- I'm buying any amount of BLURT with MXN
- I'm buying at least 40 MXN of BLURT
- I'm buying up to 70 MXN worth of BLURT
- I'm buying 40–60 MXN worth of BLURT
- I'm buying exactly 50 MXN worth of BLURT
The blog announcement is now built from that same title, so the two can never disagree again.
Smaller touches
- A clear button in the payment-method search. Once you've typed a couple of characters, a small ✕ appears in the field to empty it.
- Your settings link cards now carry their own artwork — a large globe, play or Nostr mark in the corner.
- A stray background colour is gone. Firefox tints saved-login fields its own colour; Morphit had a fix for this that only ever worked in Chrome. It works everywhere now.
- Tidier profile page. The website, streaming and Nostr links beside your avatar now sit in a consistent order, closer together, and line up with the bottom of your picture. The streaming mark is now a rounded badge rather than a bare triangle.
- Wording. The syndication card on the last step of posting is retitled, and the amount hint in the Pay window no longer says "Orders minimum".
For people running a node
Your daily backup may never have run. The built-in backup shipped in v1.8.4 used a shell option that the default shell on Debian and Ubuntu rejects, and the failure was being swallowed — so it exited silently before reaching your database, every night, while the timer reported nothing wrong. This release fixes it and adds a check that runs the script for real rather than only reading it.
Tracing that turned up several more problems on the setup path: the automated playbook installed the backup script where the service didn't look for it and never granted database access on containerised setups, the setup wizard printed a config permission the service couldn't read, and the hardening menu printed a shorter list of commands than the job needs. All corrected, with a new check keeping those files in agreement.
morphit-ops healthnow reports on backups. It shows the newest dump with its size and age, and turns red if the timer has been firing without producing anything — which is precisely the failure above. If it says a permission problem, it says so rather than claiming you have no backups.Moderation works again, and flags can now be undone. On any long-lived instance the Moderation screen crashed outright — a column existed for new installs but no upgrade ever added it. Beyond fixing that, a self-trade flag can now be cleared: honest activity can trip the detectors (two accounts set up on the same machine reviewing each other looks identical to the real thing), and the account was left with a hidden reputation card and subdued reviews. Clearing restores it immediately and permanently. The related-accounts flag clears for good, since it rests on facts that cannot change; the mutual-review flag forgives what happened so far but keeps watching, so a genuine pattern still gets caught.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.8
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 45smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 36smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 39smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 15smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 26m53smorphit-release / Build + publish release tarball (push) Successful in 27m48sreleased this
2026-07-22 06:42:16 +00:00 | 33 commits to main since this releaseNo more pop-ups from the person you're already talking to
We thought we'd fixed this last release. We hadn't — not fully. If you and someone else were chatting back and forth, every single reply was still raising a system notification, for a message you were sitting there watching arrive.
The remaining cause was a check that only counted you as "looking at the conversation" if that exact window was the one in front. Open the chat in a second window or read it on your phone, and the check decided you weren't looking — and buzzed you.
Now, if you have that conversation open, that person's messages don't raise a notification on that device. Everyone else still notifies exactly as before, as do order updates and feedback. One thing worth knowing: if you leave a conversation open and walk away, that device stays quiet for that person — your unread badge and inbox still update, and your other devices still notify normally.
The subject line appears with the message
When a new conversation arrived, the message card showed up in your inbox within a few seconds — but its subject line sat as a placeholder for about a minute before filling in with the actual listing.
The alert only tells your browser who messaged and which listing, not what the listing says. Morphit now looks that up straight away, so the card arrives complete: name, subject, and status together. Conversations that aren't about a listing no longer show a placeholder that was never going to fill in.
Tidier wallet card
Two small things on your wallet were sitting a touch low against the numbers beside them: the local-currency value next to your BLURT balance, and the little info dot next to your BP. Both now line up properly.
For people running a node
The built-in daily database backup could fail without saying why. The script is written for a shell that doesn't support one of the options it used, and the failure was being swallowed — so the backup exited silently before it ever reached your database. If you set up automatic backups on a Debian or Ubuntu server, they were not running. This release fixes that and, more importantly, adds a check that runs the script for real rather than just reading it.
While tracing that, we found and fixed several more problems on the setup path: the automated playbook installed the backup script somewhere the system service didn't look for it, and never granted database access on containerised setups; the setup wizard printed a config-file permission that the backup service couldn't read; and the hardening menu printed a shorter list of commands than the job actually needs. The docs have been corrected to match, and a new check keeps all of these files in agreement so they can't quietly drift apart again.
If you run a node, it's worth confirming you've actually seen a backup file appear — a backup you've never watched succeed isn't yet a backup.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.7
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 44smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 36smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 39smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 14smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 27m9smorphit-release / Build + publish release tarball (push) Successful in 27m35sreleased this
2026-07-22 01:12:51 +00:00 | 34 commits to main since this releaseNew messages show up in your inbox right away
When someone started a new conversation with you, the alert was instant — the notification and the little green badges lit up within a few seconds — but the message card itself could take about a minute to actually appear in your Chat inbox. You'd go looking for the message and find nothing there yet.
This release closes that gap. The moment the alert arrives, the conversation now appears in your inbox too, on the same few-second timescale — no waiting, no refreshing. Behind the scenes, the inbox was preparing an instant placeholder card for exactly this, but a tiny mismatch meant it always came up empty; that's now fixed, and pinned with a test so it can't quietly break again.
No more repeated pop-ups while you're chatting
Once two people are actively in the same chatroom, every new message was still triggering a system notification — a little pop-up for a message you're already looking at. Annoying, and pointless.
Now, while you're both viewing the same conversation, those redundant pop-ups stay quiet. You'll still get notified about messages from other people, and about everything else — this only silences the buzz for the chat that's already open on your screen.
The "Leave feedback" line tells the truth instantly
After a trade wrapped up and you left your trading partner a rating in the chatroom, going back to your inbox could still show that conversation's third line as the green Leave feedback prompt — as if you hadn't. The stars only appeared a while later.
Now the line updates the instant your rating is on-chain: no refresh, and no matter how fast you click back to the inbox, it shows the green stars you just left.
The scary red banner stops flashing during updates
Some phones and computers were seeing an alarming red "Build integrity check failed" banner during a routine update — and it could appear before the friendly "Load it now" prompt that lets you pick up the latest version. That warning is meant only for a genuinely tampered page, not for the brief moment while a new version is landing.
This release holds that banner back while an update is on its way and gives the friendly prompt time to lead, so a normal upgrade no longer sets off the alarm. The real tamper protection is unchanged — it still speaks up if a settled page ever truly doesn't match what was published.
A small wording fix
The green hint under the amount field in the Pay now window read "Orders minimum is …" — it now correctly reads "Order minimum is …".
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.6
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 45smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 38smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 40smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 14smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 27m29smorphit-release / Build + publish release tarball (push) Successful in 28m29sreleased this
2026-07-21 21:01:51 +00:00 | 35 commits to main since this releaseYour listings really do show up in the marketplace now
The last update promised that a fresh listing would appear in the marketplace the moment it was ready. It turned out that promise wasn't fully kept: a live listing could show correctly on your My Orders page yet still be missing from the main Orderbook — for you and for everyone browsing — with the page saying "No orders match your filters" even though nothing was being filtered.
We tracked it down to the real cause. The marketplace has two ways of delivering listings to your screen — a first quick load, and a live feed that keeps things fresh — and the live feed was leaving off one small label that the page uses to decide a listing is active. Without that label, the page quietly hid every listing the live feed sent. A fix a few versions ago added the label to the first quick load but missed the live feed; this release adds it there too, so both paths agree.
The upshot: post a listing, and it appears in the Orderbook and stays there — reliably, on desktop and phone. And we've added a guard so these two delivery paths can never drift apart on this again.
A quiet security update
We refreshed one of the behind-the-scenes building blocks Morphit relies on to close a newly-reported weakness in it. Nothing about how you use Morphit changes — this is pure housekeeping to keep the foundations sound.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.5
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 45smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 36smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 38smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 15smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 26m42smorphit-release / Build + publish release tarball (push) Successful in 27m17sreleased this
2026-07-21 06:38:20 +00:00 | 36 commits to main since this releaseYour new listing shows up right away — on every device
When you posted a fresh listing and paid for it, the marketplace could briefly flash your listing and then blank it — and a phone might keep showing the old view even after a refresh, all while your My Orders page correctly showed the listing as live. That's fixed. A new listing now appears reliably the moment it's ready, the marketplace always shows the freshest view instead of a stale one, and desktop and phone stay in step.
A tidier profile
The reputation card is easier to read at a glance: the No mutual-review flags pill now sits in the bottom corner, and the "last trade" note moved up to the top corner where the eye lands first. The tabs beneath it no longer show any stray scrollbars — they still slide sideways on a phone, just without the clutter. On the wallet card, the little "delegated to you" hint beside your balance lost its heavy outline and lines up more neatly.
In the reviews, the profile-link icons now appear only next to your big profile picture at the top — nowhere else — and each review reads a little cleaner: a simple Rated me: with the reviewer already named just above, and no repeated name in front of their comment.
A cleaner settings page
A few buttons that never earned their place are gone: the redundant Clear buttons on the website, streaming, and Nostr link cards. In the notifications section, the note explaining background alerts now spans the full width instead of being squeezed into a narrow column. Your avatar's "this is permanent" warning now steps aside once you've already set a picture. And the Nostr link box no longer trips your password manager into offering to fill it — it's a web address, and now it behaves like one.
Smaller touches
When you're choosing what to sell and you tap an asset to read its help tip, the tip now disappears the instant you move your pointer away, instead of lingering. And in a chat, the "nobody else can read this" reassurance now tucks in just below the message box, so there's no wasted gap under it.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.4
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 43smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 35smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 38smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 14smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 26m7smorphit-release / Build + publish release tarball (push) Successful in 26m58sreleased this
2026-07-21 02:26:55 +00:00 | 37 commits to main since this releaseThe marketplace reliably shows every live listing again
A recent update could leave the marketplace looking empty even when there were listings to see. That's fixed — the orderbook now shows every live listing reliably, so buyers find your offers and you find theirs. And if the book ever genuinely has nothing to show, you now get a friendly "no listings yet" note instead of a blank space.
A cleaner, easier-to-read profile
Each profile now gathers its details into simple tabs under the reputation card — Reviews received, Reviews given, and Active orders — so a long scroll becomes a tidy card you can flip through. On your own profile you'll also see a Trade history tab with your completed trades. The tabs slide sideways on a phone so they always fit, and you can move between them with the arrow keys.
A trust signal you can read at a glance
The reputation card now shows a small green pill — No mutual-review flags — when an account shows no sign of the "you review me, I review you" pattern that can quietly inflate ratings. If our checks ever spot that pattern, the pill turns amber so you know to look a little closer.
Your profile links, right where you'd expect
If you've added a website, a streaming page, and a Nostr link, their icons now sit neatly to the right of your big profile picture — evenly spaced and nowhere else on the page. And on the settings page, the Save button for your website address now works as it should.
Help tips that point at the right word
Hover or tap an underlined term inside a help article and its explanation now appears right next to the word, instead of drifting off to a corner of the screen.
Your new listing stays put while it posts
When you post a listing, the gentle "Posting…" note on your My Orders page now shows a short countdown and stays visible until your real listing lands — no more watching it quietly disappear before it's ready.
A few tidy-ups
The wallet card is a little cleaner — any Blurt Power delegated to you now tucks behind a small tappable icon beside your balance instead of taking its own line. The profile-link settings dropped some redundant preview boxes, the star on each chat card moved into the corner so longer names have room to breathe, and a handful of labels read a little clearer.
Your data, your keys, your trades — all untouched throughout.
Downloads
-
Morphit v1.8.3
StableAll checks were successfulmorphit-ci / TypeScript typecheck (sweep all workspaces) (push) Successful in 46smorphit-ci / apps/web svelte-check (svelte-kit sync + svelte-aware tsc) (push) Successful in 36smorphit-ci / Integration tests (real Postgres 16) (push) Successful in 38smorphit-ci / ansible-lint (playbook quality gate) (push) Successful in 15smorphit-ci / Smoke suite (run-smokes.sh, triple-pulse) (push) Successful in 27m0smorphit-release / Build + publish release tarball (push) Successful in 27m54sreleased this
2026-07-20 17:55:51 +00:00 | 38 commits to main since this releasePaying and getting paid now feels solid
When you send a BLURT payment, the receipt now says "Verifying…" while the blockchain confirms it — instead of briefly flashing a worrying "couldn't verify" message the very moment you hit send. That flash was never a real problem; a payment simply needs a few seconds to settle into a block before it can be checked, and now the receipt waits calmly for that instead of crying wolf.
Both you and the other person watch the receipt turn to a clear confirmation the instant the payment lands, and the top of the conversation flips to show (Paid). Once a trade is paid, the listing leaves the marketplace quickly, so nobody messages you about something that's already done.
Your new listing appears the moment you post it
Post a listing and it shows up on your My Orders page right away with a gentle "Posting…" note, rather than leaving you staring at an empty page while the network catches up. New message conversations appear the same way — the moment the first message arrives, the thread is there.
If you'd like to promote a fresh listing, the "set up a featured bid" link now takes you straight to that exact listing, and its Feature button lights up the second the listing goes live.
See the state of any conversation at a glance
The top of each chat now shows whether the listing it's about is (Live), (Canceled), (Expired), or (Paid). So when you reopen an older conversation, you can tell in a second whether the thing you were negotiating still exists — and whether it's already been paid for.
A tidier My Orders, and a cleaner chat
The Edit button on each of your listings now carries its own small countdown — ✏️ Edit · 7:22 — instead of a separate tag floating above an oversized button, and all the action buttons line up neatly at the same width. The BLURT payment screen has less clutter, and the payment receipt now has a copy button for the transaction ID, so you can grab it in one tap.
No more scary red banner after an update (especially on phones)
Right after Morphit updated itself, some people — most often on phones — saw an alarming red "build integrity check failed" banner that only cleared after refreshing a second time. That was a false alarm from the update still settling in, and it's gone now. The genuine safety check that protects you from a tampered copy of the app is completely untouched — it just no longer mistakes a normal update for a problem.
Clearer wording
A few small wording tidy-ups, including the subtitle on your My Orders page.
Your data, your keys, your trades — all untouched throughout.
Downloads