Releases: MostroP2P/mostro
v0.12.4
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- New actions and remove text strings, refactoring by @Catrya in #340
- Pow check of events incoming by @arkanoider in #341
- Include dispute id on dispute start by @grunch in #343
Full Changelog: v0.12.3...v0.12.4
v0.12.3
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- now cooperative cancelled order are no more managed by admin by @arkanoider in #317
- Added scheduler event with relay list by @arkanoider in #319
- fix for issue #320 by @arkanoider in #321
- Update nostr event by @grunch in #326
- Add new order event spec page by @grunch in #328
- Introduces a in-memory price cache by @bilthon in #329
- cosmetics on duplicated code by @arkanoider in #332
- Simple idea for cancel take by @arkanoider in #331
- starting idea for resubscribe of invoices held by @arkanoider in #330
- Removing some unwraps to cool down my mind by @arkanoider in #336
Full Changelog: v0.12.2...v0.12.3
v0.12.2
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- New mostro install guide by @grunch in #298
- Fix how we publish range fiat amount by @grunch in #300
- hot fix on range order implementation by @grunch in #301
- Prohibits buyers from stealing orders by @grunch in #308
- Add Docker setup and guide for building and running MostroP2P by @tincho70 in #307
- Add return on takesell function by @grunch in #309
New Contributors
Full Changelog: v0.12.1...v0.12.2
v0.12.1
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- Add range order docs by @grunch in #287
- fix #288 by @arkanoider in #290
- Add contributing guide by @grunch in #292
- doc: updates the 'add-invoice' content by @bilthon in #293
- bumped nostr-sdk by @arkanoider in #296
- added maker rating on new order creation by @arkanoider in #291
- Quick fix for rate user on order creation by @arkanoider in #295
- feat: handles message parsing error & prints an error log by @bilthon in #294
- fix typos on mostro v0.12.0 by @arkanoider in #297
Full Changelog: v0.12.0...v0.12.1
v0.12.0
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- Set the right gzip file extension by @grunch in #281
- [docs] Fix error on dispute message by @grunch in #283
- Upgrade dependency by @grunch in #282
- Range order fixes by @arkanoider in #286
Full Changelog: v0.11.6...v0.12.0
v0.11.6
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- Removed other unwraps and minor cosmetics by @arkanoider in #272
- bumped some deps and removed two unwraps by @arkanoider in #273
- nip40 expiration event by @arkanoider in #274
- Idea for fix issue #264 by @arkanoider in #277
- Info mostro message by @arkanoider in #279
Full Changelog: v0.11.5...v0.11.6
v0.11.5
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
Once you have the required PGP keys, you can verify the release (assuming manifest.txt.sig and manifest.txt are in the current directory) with:
gpg --verify manifest.txt.sig manifest.txt
gpg: Firmado el jue 03 ago 2023 15:07:05 -03
gpg: usando RSA clave 1E41631D137BA2ADE55344F73852B843679AD6F0
gpg: Firma correcta de "Francisco Calderón <fjcalderon@gmail.com>" [absoluta]
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
- small fix to return from settle_seller_hold_invoice if there are errors by @arkanoider in #269
- This PR allows cross platform compilation by @grunch in #271
Full Changelog: v0.11.4...v0.11.5
v0.11.4
What's Changed
- Added the check on min sats allowed in a new order by @arkanoider in #261
- Idea to catch the great part of the errors by @arkanoider in #259
- Remove of some unwraps by @arkanoider in #262
- Solvers should take disputes before operate by @grunch in #267
- Stop sending CantDo message after solver settles dispute by @grunch in #268
Full Changelog: v0.11.3...v0.11.4
v0.11.3
v0.11.2
What's Changed
- New actions added to docs by @grunch in #242
- Send solver pubkey to both parties by @grunch in #244
- Limit size of messages by @grunch in #243
- Changing routing fee rules by @grunch in #245
- Allow admin actions to be done by solvers by @grunch in #246
- Makers can't take own orders by @grunch in #247
Full Changelog: v0.11.0...v0.11.2