fullmetalScience

For this release I made sure that the various NoShore tools can be run side-by-side on the same machine, as the same user.

This means that you can now team up ghost and gate locally to use them together with a tower-instance, local or remote.

The commands you need in order to issue a transaction can look like this:

gate dest 888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H
gate cost 0.1776
ghost trigger

That's the boring way, though. Ever wondered how come no website ever provides you a complete string you can just copy and paste to your Monero CLI - like transfer 888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H 0.1776?

While we keep wondering, NoShore handles this gracefully for us, allowing websites to keep doing their thing.

Let's say they prompt for payment like this: "Send 0.1776 Monero to 888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H". Instead of plumbing together the corresponding transfer-command, simply have gate handle it:

gate scan "Send 0.1776 Monero to 888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H"

It will discard anything useless, tell you what remained and set dest and cost accordingly.

For added serenity you can run gate help to see the parameters once again before you execute ghost trigger just as before.

And now for the geeks: QR code scanning++

(as if NoShore wasn't geeky by design :)

Run scan without parameters, use your camera and process a string like the one from the previous example directly from a QR code:

# As seen in this post's image
gate scan

Currently, this is Termux-only, but it can work just as well with your PC's camera.

Installation

To activate all of the above, be sure to clone the current version, v0.2.0:

git clone --branch v0.2.0 \
    https://git.sr.ht/~fullmetalscience/noshore \
    ~/xmr.zone/noshore

Remember to install the optional dependencies as suggested by gate setup.

Why use NoShore as Wallet?

Efficiency, for starters: No sync wait, no battery use - just three commands that sign as fast as tower can plug together the outputs of a new transaction.

Then, having NoShore as daily Monero-driver boosts its development by noticing bugs early.

There's also the configurable donation on tower (just grep for "donate"), so simply using the tool already motivates development.

And finally, if we want merchants to start adopting the concept for payments, we better have our side of the deal in place.

NoShore's on xmr.zone.

With some delay but much dedication the first version of NoShore is now completed.

Its concept is to make payments simpler for end-users by transferring some of the burden to merchants and back-ends.

The back-end prepares transactions, so that all that remains to do for the user's device is to sign them.

While, technically, this allows users to stay offline throughout the process, it is important to understand that the reasoning for going this route is not security.

Instead, it is to reduce complexity, so that Monero may become accessible to broader audiences apart from tech-enthusiasts.

The section "The Big Picture" on the project site describes what NoShore's usage could look like once fully developed.

NoShore's on xmr.zone.

As a runner-up to NoShore offline payments, its basis, XMRPC has received lots of improvements which are are now published and tagged as version 0.3.0, thereby leaving the beta-phase behind.

Highlights

• Validators for address/height/key
• Colorized output
• Wallet-switching

Find further details in the documentation or download the new version directly:

If you haven't previously cloned XMRPC

git clone --branch v0.3.0 \
    https://gitlab.com/fullmetalScience/sxmo-onfire.git

If you are working with an existing clone

git fetch origin tag v0.3.0
git checkout tags/v0.3.0

See also: previous release (v0.2.0-beta), initial announcement

For years, I've been unable to let go of the vision of creating the simplest payment-interface possible.

I couldn't find the required specialists to outsource some challenging parts of my initial design.

Now, thanks to a discussion with the developer of XmrSigner - plus the interest of someone specialized in FPGA's, I realized that I could create a major part of the functionality and, from there, follow a clear path forward.

Please feel free to review the linked CCS-draft - any workable feedback is welcome!

cross-posted from: https://monero.town/post/2936546

While our XMR.ID stagenet test is about to conclude, I've taken the time to polish and publish another piece from my Sxmo collection - a set of tools that should help simplify your everyday Monero use on desktop, terminal and mobile.

It's called units and is intended to be used as your main calculator and friendly companion for quick XMR rate-conversions.

Details: https://xmr.zone/sxmo-onfire/units/

Feel free to report any issues.

PS: The first piece of the collection is codes, a means of monitoring gift card spending and balances. It was published in September and announced on XMR.ID's Matrix.

I would like to incentivize timely (1-2 months max.) implementation of pmOS camera-support for SDM845 devices by offering a bounty of 6 XMR (Monero, the digital cash). The intent to win the bounty has to be discussed here beforehand.

If supporting the entire list of devices implies significantly more effort than a subset, the minimum should be OnePlus and Shift. Details from comment:

When one opens a camera application (like millipixels), the screen should show what the camera points at and capturing color photo and video of that content should be possible. It should run in a stable manner (meaning no anticipated crashes) and the required changes should be accepted into the postmarketOS edge branch.

If bounties happen to be against the ethos of the project, let me know.

On the contrary, I hereby invite others to chip in.

Comment if interested.