Skip to content

Releases: MostroP2P/mostro

Release v0.17.4

22 May 20:46
v0.17.4
187a4cc

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/catrya.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider, manifest.txt.sig.catrya and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt
gpg --verify manifest.txt.sig.catrya manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 9A718444050F091D3D24CF6CE15E232F243D73E6
gpg: Good signature from "Catrya (github) <140891948+Catrya@users.noreply.github.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.17.4

🚀 Features

  • feat(bond): Phase 3.5 — payout confirmation to the winner by @grunch in #743
  • feat(bond): Phase 3 — payout flow for slashed bonds by @grunch in #738
  • feat(bond): Phase 2 — solver-directed dispute slash by @grunch in #737
  • feat: support MOSTRO_NSEC_PRIVKEY env var for Nostr private key by @AndreaDiazCorreia in #713
  • feat(bond): Phase 1.5 — dedicated PayBondInvoice action + WaitingTakerBond status by @grunch in #736
  • feat(bond): concurrent taker bonds, first-to-lock wins (Phase 0+1) by @grunch in #733
  • feat(bond): align AntiAbuseBondSettings with spec — slash split, claim window, drop unused dispute flag by @grunch in #728
  • feat(bond): add Forfeited terminal state for long-stop bond payout by @grunch in #727
  • feat(bond): add Phase 0 schema columns for split, forfeit window, and retry separation by @grunch in #726
  • feat: added catrya key for manifest signature by @Catrya in #724
  • feat(bond): anti-abuse bond phase 1 — taker lifecycle (lock + always release) by @grunch in #719
  • feat(nip59): adopt mostro-core 0.10.0 dual-key gift wrap transport by @grunch in #718
  • feat(bond): anti-abuse bond phase 0 foundation by @grunch in #712

🐛 Bug Fixes

  • fix(price): tolerate null rates in Yadio /exrates/BTC response by @grunch in #748
  • fix: include created_at on AddInvoice SmallOrder by @arkanoider in #739
  • fix(bond): align bond invoice memo with spec §6.1 by @grunch in #735
  • fix(restore-session): re-send AddInvoice for failed payments on session restore by @codaMW in #721

💼 Other

  • Update CHANGELOG for version 0.17.4 by @grunch
  • Revert "fix(restore-session): re-send AddInvoice for failed payments on session restore" by @grunch in #722
  • Add read and read-write dispute solver permissions by @mostronatorcoder[bot] in #708

📚 Documentation

  • docs: spec for multi-source price providers (remove Yadio single point of failure) by @grunch in #745
  • docs(bond): add Phase 3.5 — payout confirmation to the winner by @grunch in #742
  • docs(bond): fold taker_* columns into Phase 0 schema by @grunch in #734
  • docs(bond): switch Phase 1.5 to concurrent taker bonds, first-to-lock wins by @grunch in #732
  • docs(bond): spec cancel_action handling for WaitingTakerBond status by @grunch in #730
  • docs(bond): note that mostro-core 0.11.0 ships Phase 1.5 + Phase 2 variants by @grunch in #729
  • docs(bond): decouple slash from trade outcome; clarify maker/taker vs… by @grunch in #725

⚙️ Miscellaneous Tasks

  • Release mostro version 0.17.4 by @grunch

Contributors

Full Changelog: v0.17.3...v0.17.4

Release v0.17.3

10 Apr 22:20
v0.17.3
d0787dd

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.17.3

🐛 Bug Fixes

  • fix: fix for bug introduced in 0.17.2 blocking range orders by @arkanoider in #705

💼 Other

  • Update CHANGELOG for version 0.17.3 by @grunch

⚙️ Miscellaneous Tasks

  • Release mostro version 0.17.3 by @grunch

Contributors

Full Changelog: v0.17.2...v0.17.3

Release v0.17.2

10 Apr 12:01
v0.17.2
2d96531

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.17.2

🚀 Features

🐛 Bug Fixes

💼 Other

  • Update CHANGELOG for version 0.17.2 by @grunch
  • Include solver_pubkey in restore disputes response by @BraCR10 in #690

⚙️ Miscellaneous Tasks

  • Release mostro version 0.17.2 by @grunch

Contributors

Full Changelog: v0.17.1...v0.17.2

Release v0.17.1

27 Mar 20:42
v0.17.1
d6de05f

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.17.1

🚀 Features

💼 Other

📚 Documentation

🧪 Testing

  • test: add end-to-end y-tag emission coverage for order/info/dispute/admin/dev-fee events by @codaMW in #668

⚙️ Miscellaneous Tasks

  • Release mostro version 0.17.1 by @grunch
  • Improved github actions: bumped action for checkout and also MSRV version by @arkanoider in #687

Contributors

Full Changelog: v0.17.0...v0.17.1

Release v0.17.0

18 Mar 17:57
v0.17.0
f9d77da

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.17.0

💼 Other

  • Update CHANGELOG for version 0.17.0 by @grunch

🚜 Refactor

📚 Documentation

⚙️ Miscellaneous Tasks

  • Release mostro version 0.17.0 by @grunch

Contributors

Full Changelog: v0.16.5...v0.17.0

Release v0.16.5

13 Mar 14:26
v0.16.5
f8e5647

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.16.5

💼 Other

🚜 Refactor

🧪 Testing

⚙️ Miscellaneous Tasks

◀️ Revert

Contributors

Full Changelog: v0.16.4...v0.16.5

Release v0.16.4

09 Mar 22:39
v0.16.4
7cc6c82

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.16.4

🚀 Features

🐛 Bug Fixes

💼 Other

  • Update CHANGELOG for version 0.16.4 by @grunch
  • Deduplicate db test helpers by @grunch in #629
  • Automated badge for toolchain and version in README.md by @arkanoider in #628
  • Fix restore session dispute initiator by @BraCR10 in #599

🚜 Refactor

  • refactor: extract dev fee logic into dedicated module by @arkanoider in #627

📚 Documentation

⚙️ Miscellaneous Tasks

  • Release mostro version 0.16.4 by @grunch

Contributors

Full Changelog: v0.16.3...v0.16.4

Release v0.16.3

20 Feb 10:05
v0.16.3
48396a1

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.16.3

🚀 Features

  • feat(docker): plain image, settings.tpl.toml, StartOS as mostro-startos by @arkanoider in #597

🐛 Bug Fixes

  • fix: prevent buyer_invoice leak to seller in DM payloads by @Catrya in #609

💼 Other

  • Update CHANGELOG for version 0.16.3 by @grunch
  • Add configurable per-kind event expiration to prevent storage bloat by @mostronator in #603
  • Fix Docker DB password startup flow by @grunch in #604

⚙️ Miscellaneous Tasks

  • Release mostro version 0.16.3 by @grunch

Contributors

Full Changelog: v0.16.2...v0.16.3

Release v0.16.2

12 Feb 14:40
v0.16.2
5ea5caf

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.16.2

🐛 Bug Fixes

  • fix: prevent redundant LND queries for confirmed dev fee payments by @mostronator in #586
  • fix: check LN payment status before resetting on dev fee timeout by @mostronator in #582
  • fix: prevent duplicate dev fee payment on timeout by @mostronator in #584
  • fix: add rate limiting to ValidateDbPassword RPC endpoint by @mostronator in #580
  • fix: close active dispute when order is cooperatively canceled by @mostronator in #578

💼 Other

  • Update CHANGELOG for version 0.16.2 by @grunch
  • update readme: add mostrix and mobile client, remove mostro-web by @Catrya in #576

📚 Documentation

  • docs: add fenced code block language specifier guideline to AGENTS.md by @mostronator in #579

⚙️ Miscellaneous Tasks

  • Release mostro version 0.16.2 by @grunch
  • chore: update Rust toolchain from 1.90.0 to 1.93.0 by @mostronator in #581

Contributors

Full Changelog: v0.16.1...v0.16.2

Release v0.16.1

08 Feb 16:17
v0.16.1
1e6c205

Choose a tag to compare

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/negrunch.asc | gpg --import
curl https://raw.githubusercontent.com/MostroP2P/mostro/main/keys/arkanoider.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig.negrunch, manifest.txt.sig.arkanoider and manifest.txt are in the current directory) with:

gpg --verify manifest.txt.sig.negrunch manifest.txt
gpg --verify manifest.txt.sig.arkanoider manifest.txt

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Good signature from "Francisco Calderón <fjcalderon@gmail.com>" [ultimate]

gpg: Signature made fri 10 oct 2025 11:28:03 -03
gpg:                using RSA key 2E986CA1C5E7EA1635CD059C4989CC7415A43AEC
gpg: Good signature from "Arkanoider <github.913zc@simplelogin.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

What's Changed in v0.16.1

🚀 Features

  • feat: Publish NIP-01 Kind 0 metadata on startup by @grunch in #575

💼 Other

  • Update CHANGELOG for version 0.16.1 by @grunch
  • Inconsistent Version Tag Format in CHANGELOG by @grunch
  • Missing Admin Participant Declaration in Mermaid Diagram by @grunch

📚 Documentation

  • docs: Remove hardcoded line numbers and add guideline against them by @grunch in #573
  • docs: Fix dev_fee calculation timing contradictions in DEV_FEE.md by @grunch in #571

⚙️ Miscellaneous Tasks

  • Release mostro version 0.16.1 by @grunch

Contributors

Full Changelog: v0.16.0...v0.16.1