# Grin product wishlist

**URL:** https://forum.grin.mw/t/grin-product-wishlist/9704
**Category:** Development and Technical Discussion
**Created:** [April 14, 2022, 5:09pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704 "2022-04-14T17:09:40Z")
**Posts on this page:** 20
**Page:** 3

<div class="post-metadata">

### Author: ![Anynomous](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/anynomous/32/2928_2.png) [@Anynomous](https://forum.grin.mw/u/Anynomous)
#### Post date: [March 21, 2024, 11:47am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/44 "2024-03-21T11:47:55Z")

</div>

Cool ideas 🕶 !  
Having the wallet on a USB is already possible, you can run grin-wallet defining its location.  
For example, you can even have the whole wallet software on the USB stick and run in like:  
`grin-wallet.exe init --here`  
When you run it this way from a USB stick all the wallet data will be put in the same directory as grin-wallet.exe on the USB stick. When you unplug the USB, your funds will be completely safe from hackers.  
If you also run the node software from the USB stick, there would not even be any trace that you used Grin on your computer after you unplug it. Rather cool when I think about it.

🤔 I do not think there are many crypto projects that could put the full nodes chain data on 10$ USB stick like you can do with Grin 😄 !

Even cooler IMO would be to run a wallet air-gaped, which would require some extra software, see [this bounty proposal](https://forum.grin.mw/t/funding-proposal-2-bounty-for-a-hardware-wallet-implementation-bounty/10600) 🙂.

Regarding a plug-in miner, Grin has the advantage of grin mining being memory limited and not so power hungry, meaning powering a small chip through USB might actually be possible. On the downside, the chip would require lot of fast memory since cuckoo cycle is memory bound, which would mean a chip would easily become expensive making it very hard to compete with a G1 mini,

---

<div class="post-metadata">

### Author: ![navie](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/navie/32/4201_2.png) [@navie](https://forum.grin.mw/u/navie)
#### Post date: [March 21, 2024, 1:05pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/45 "2024-03-21T13:05:40Z")

</div>

> [@Anynomous](#):
>
> 🤔 I do not think there are many crypto projects that could put the full nodes chain data on 10$ USB stick like you can do with Grin 😄 !

Precisely! It would be a fun and affordable little product to sell as a primer for those interested and holding Grin long-term or for those wanting to store in “cold storage”. 😁

> [@Anynomous](#):
>
> the chip would require lot of fast memory since cuckoo cycle is memory bound

Good point. I think it _may_ be possible but I am not familiar enough with chip hardware or design (nor have I done any research on this).

Any ideas for potential chip candidates? I was actually thinking more along the lines of a GPU implementation using the C31 algorithm but this presents its own set of challenges.

---

<div class="post-metadata">

### Author: ![trab](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@trab](https://forum.grin.mw/u/trab)
#### Post date: [March 21, 2024, 5:47pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/46 "2024-03-21T17:47:41Z")

</div>

> [@navie](#):
>
> It would be a fun and affordable little product to sell as a primer for those interested and holding Grin long-term or for those wanting to store in “cold storage”.

My whole operating principle is that there is no point in catering to cold storage for long term saving if we have no utility in the short term. There will _be_ no long term without a short term.

For that reason, I would like to see a heavier focus on improving the utility of Grin for _today_, in every day use. To me, this means making Grin viable for buying and selling. Making a Venmo product, for example [Venmo/Cashapp product planning](https://forum.grin.mw/t/venmo-cashapp-product-planning/9714) Making it compatible with escrows [Grin Escrow product planning](https://forum.grin.mw/t/grin-escrow-product-planning/10818) and more

---

<div class="post-metadata">

### Author: ![cryptodahu](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/cryptodahu/32/5774_2.png) [@cryptodahu](https://forum.grin.mw/u/cryptodahu)
#### Post date: [March 23, 2024, 8:15am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/47 "2024-03-23T08:15:28Z")

</div>

1. node + mining + wallet on Raspberry5 like Piaxe ([About Piaxe | Wiki](https://osmu.wiki/piaxe/about))
2. Grin Wallet on Raspberry Umbrel

---

<div class="post-metadata">

### Author: ![transatoshi](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/transatoshi/32/6247_2.png) [@transatoshi](https://forum.grin.mw/u/transatoshi)
#### Post date: [April 3, 2024, 7:27pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/48 "2024-04-03T19:27:36Z")

</div>

You should be able to run grin server as a daemon aka headless in the background. The GUI/TUI is nice looking, but I wish I could add grin server as a crown job @reboot so my node is executed at startup windowless.

If no one with the proper expertise is willing to do it, I’ll add it to my list of tasks related to learning about Grin and it’s finer details.

---

<div class="post-metadata">

### Author: ![Anynomous](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/anynomous/32/2928_2.png) [@Anynomous](https://forum.grin.mw/u/Anynomous)
#### Post date: [April 4, 2024, 7:01am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/49 "2024-04-04T07:01:37Z")

</div>

That is possible, just check ./grin --help. This question was asked before, so should be on the forum.

---

<div class="post-metadata">

### Author: ![transatoshi](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/transatoshi/32/6247_2.png) [@transatoshi](https://forum.grin.mw/u/transatoshi)
#### Post date: [April 4, 2024, 9:43am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/51 "2024-04-04T09:43:26Z")

</div>

Found it in grin-server.toml I must have skipped over it when configuring

 ![Screenshot from 2024-04-04 02-42-28](https://canada1.discourse-cdn.com/flex036/uploads/grin/original/2X/2/25a802c70e8554dbb473495c246e312bc2c4f52f.png)

Would be nice to be able to use as a command flag, but this is just fine for me. Although it’s not quite in the background all the way as it’s not returned to the prompt. I have submitted an issue ticket for this on Github.

 ![Screenshot from 2024-04-04 02-46-00](https://canada1.discourse-cdn.com/flex036/uploads/grin/original/2X/b/b752436f75f3b4deb70b12a76ac5afc72811616c.png)

EDIT: I found the solution and it’s very Grin-ish, it’s in this Medium article:

[GRIN Full node and Wallet Installation Linux](https://privatepayments1.medium.com/grin-full-node-and-wallet-installation-linux-9025684802fa)

First install grin to /usr/local/bin which everyone should along with creating both a new user and group called grin to run the daemon, then you have to manually create the grin.service file and reload systemctl daemon , enable grin.service and run.

It doesn’t play super nice with grin-wallet either. It spits out a bunch of errors while starting the listener.

---

<div class="post-metadata">

### Author: ![trab](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@trab](https://forum.grin.mw/u/trab)
#### Post date: [September 13, 2024, 6:06pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/52 "2024-09-13T18:06:00Z")

</div>

Bumping this thread again with some things that are still in the forefront of my mind:

1. [Grin node for Umbrel](https://forum.grin.mw/t/grin-node-on-umbrel-rpi-4/11061)
2. [Venmo/Cashapp style Wallet](https://forum.grin.mw/t/venmo-cashapp-product-planning/9714) (Grim?)
3. [Marketplace](https://forum.grin.mw/t/marketplace-product-planning/10429) and [Escrow service](https://forum.grin.mw/t/grin-escrow-product-planning/10818)
4. [Grin powered Messenger](https://forum.grin.mw/t/keychat-nostr-messenger/11185)

---

<div class="post-metadata">

### Author: ![Grinception](https://avatars.discourse-cdn.com/v4/letter/g/f0a364/32.png) [@Grinception](https://forum.grin.mw/u/Grinception)
#### Post date: [October 23, 2024, 9:52am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/54 "2024-10-23T09:52:18Z")

</div>

I have a friend who still plays D2 and often buys and sells items via a forum, which has its own currency. You cannot transfer is currency or anything so its more like a internal thing for this community, at least in my understanding.

If we could make it easy for developers to integrate Grin instead of making their own internal reward systems and make it easy to accept grin for micropayments + integrated atomic swap functionality this would be a powerful stack imo. Maybe also with the option for the admin to charge a fee on the transfers (to give an incentive to use it), this in total would be a superior option.

My logic is that if its really easy to implement, people will build something with it which would lead to usage. Unfortunately I dont see how anyone in the real world would accept it as a means of payment for anything valuable, considering that you cannot buy anything with it and that its not that easy to exchange for money.

EDIT: Not sure if I am allowed to share a link but here it is: [https://www.d2jsp.org/](https://www.d2jsp.org/)

---

<div class="post-metadata">

### Author: ![Arka](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/arka/32/6134_2.png) [@Arka](https://forum.grin.mw/u/Arka)
#### Post date: [October 23, 2024, 1:03pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/55 "2024-10-23T13:03:36Z")

</div>

Indeed, if we can provide tools that facilitate the easy integration of GRIN as a payment method, it would greatly boost its adoption. For example, a WordPress plugin could be one such tool

---

<div class="post-metadata">

### Author: ![trab](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@trab](https://forum.grin.mw/u/trab)
#### Post date: [February 24, 2025, 4:45am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/56 "2025-02-24T04:45:34Z")

</div>

Torrent seeding rewarded with grin?

Just saw this nostr+webtorrent+bitcoin project

> **[BitVid - Decentralized Video Sharing](https://bitvid.network/)**
>
> Share videos and follow creators freely, in a truly decentralized way.

---

<div class="post-metadata">

### Author: ![Cobragrin](https://avatars.discourse-cdn.com/v4/letter/c/aca169/32.png) [@Cobragrin](https://forum.grin.mw/u/Cobragrin)
#### Post date: [February 24, 2025, 9:08am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/57 "2025-02-24T09:08:53Z")

</div>

This is a real use case 👍 for Grin, apart from exchanges.

---

<div class="post-metadata">

### Author: ![trab](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@trab](https://forum.grin.mw/u/trab)
#### Post date: [February 28, 2025, 6:24pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/58 "2025-02-28T18:24:55Z")

</div>

> [@Grinception](#):
>
> My logic is that if its really easy to implement, people will build something with it which would lead to usage

What would make something easy or not easy to implement?

I’m guessing that just being a js library would make it easy. And that is actually on the roadmap for after the Python implementation [https://raw.githubusercontent.com/grinventions/about/refs/heads/main/graphics/roadmap.png](https://raw.githubusercontent.com/grinventions/about/refs/heads/main/graphics/roadmap.png)

I think the most crucial component missing right now is the payment proof verifier

---

<div class="post-metadata">

### Author: ![trab](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@trab](https://forum.grin.mw/u/trab)
#### Post date: [March 7, 2025, 3:10am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/59 "2025-03-07T03:10:49Z")

</div>

> [@trab](#):
>
> I think the most crucial component missing right now is the payment proof verifier

The tough thing is that payment proofs are not the killer app. The stuff that is built _with_ the payment proofs are the killer apps.

Stuff like new contract flow and payment proofs are not sexy. They’re not attractive to developers. Wallets, marketplaces, bots, messengers, torrenting, these things are sexy.

---

<div class="post-metadata">

### Author: ![Anynomous](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/anynomous/32/2928_2.png) [@Anynomous](https://forum.grin.mw/u/Anynomous)
#### Post date: [March 7, 2025, 8:44am UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/60 "2025-03-07T08:44:32Z")

</div>

What is it we actually need right now regarding Payment Proofs? Is it that there is a bug that needs fixing? I though bidirectional payment proofs are in the _grin-wallet_ Contract Branch code. Or do we need an external verifier for payment proofs (not that private), or is it that there is no support for payment proofs in GUI wallets like Grim and Grin++?  
Sorry, I am to lazy to check all the details myself, beside we should distribute, being on top of everything is too much.  
If it is just a bug, perhaps I can have look at it and see if I can fix it.

---

<div class="post-metadata">

### Author: ![Yeastplume](https://avatars.discourse-cdn.com/v4/letter/y/71c47a/32.png) [@Yeastplume](https://forum.grin.mw/u/Yeastplume)
#### Post date: [March 8, 2025, 12:30pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/61 "2025-03-08T12:30:59Z")

</div>

Early payment proofs working and enabled by default in the contracts branch of the wallet, see related PR here:

> <https://github.com/mimblewimble/grin-wallet/pull/681>
>
> Following on from experimental slate V5, changes, this aims to implement an expe…rimental version of \[early proofs\](https://github.com/tromp/grin-rfcs/blob/early-payment-proofs/text/0000-early-payment-proofs.md) into the \`contracts\` branch. Note that \`legacy' transaction workflows are not affected.
> 
> \* Add required arguments structures and definitions
> \* Add initial test for development purposes
> \* (TBD)
> 
> Other notes
> \* signature for proof type \`Invoice\` is automatically generated by default. Generating another proof type or omitting proof requires \`opting out\` at present (subject to discussion)

Really, the best way to get payment proofs live would be to get the experimental contracts branch working within Grim and test,test,test to the point where we’d be comfortable merging all of the work in the contracts branch to master.

---

<div class="post-metadata">

### Author: ![ardocrat](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.grin.mw/ardocrat/32/5164_2.png) [@ardocrat](https://forum.grin.mw/u/ardocrat)
#### Post date: [March 8, 2025, 12:44pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/62 "2025-03-08T12:44:47Z")

</div>

Hello, one community member tried to test proofs with grin-wallet and got an issue:

> <https://github.com/mimblewimble/grin-wallet/issues/729>
>
> Wallet 1:
> \`\`\`
> ./target/release/grin-wallet --testnet contract new --send=1 --e…ncrypt-for=tgrin1pj5wlv3nhvua5lgr72dq9ufu8aw2m05ke5z47j5463zvrgej54qsstc3rg
> Password: 
> \--------------- SLATEPACK METADATA --------------
> 
> Slate encrypted: true
> Slate finalized: false
> Slate saved to file: /slatepack/3198ee9b-f033-4e6e-8699-19c9cb58f82d.S1.slatepack
> 
> \-------------- CUT BELOW THIS LINE --------------
> 
> BEGINSLATEPACK. 3pDmAZBPAaFKxhX Hhi1beNF3pCpmpY ugZNstfhxHzQtrZ zA9HUtMTgbXmUa6 FHQAqRSa3U1fwbu D3iaiYSPLT1hjTE qGMm2rdsVyBofM6 cp6ZDe7Lm3bEm2b 7jmdrzGyfPSTNrL fWrceZbM7rKFo59 bST38KxMXginKca Y7JcQbrJoETKc2W WY6vNTWzfg9QJBt PyDUZhzmMP9KYWT ECjhaagFWtxxfKw pTPMUxgQX6kdbGx NnfuJavCv658VAR ka9upRnBD3ti5MP 27iXnvFYZEpgHJc 4UQF4PutVPdBt2r pXTQ3dRx4bAmDAk j4RG9Y4wMv2h5sc XTKHJP8pHVZGk9n vqeYQWNEK5reqUX rtK4oyA63wCmq9D r75BTjwPn9vdqma eeb9oazDpALNDCn XtguxrSwoPn7coM iCUdCvGKeigZ3rw SokXdb7x8L6x7Ej 3QimTEkg9DoJFe6 FJsEGG5dFQMfzBK 9nEHGvaLt5c2MT3 MBd1FMi9p1fMGmm r7B7bNCMMqpZm6c 7Vfc4F7T4AFRyvF WFbgzGJsafYvfNq oLfZ4vfBquVBaW3 DFsKRBMXnvaA1xy n2L1MqziRyEzGSU BRtmt4xeU3jFtZY HnhsdryC5TdiTV3 i1G6pN6mhJdCXvW nbc51S4HV4gspJJ 3Tw7k2GTt8B4hHC 4Ms93g93PkA2SDZ P19zYouaeerg6iT ScxPXuiZXbC2pZ. ENDSLATEPACK.
> 
> \-------------- CUT ABOVE THIS LINE --------------
> Command 'contract' completed successfully
> \`\`\`
> 
> Wallet 2:
> \`\`\`
> ./grin-wallet --testnet contract sign --receive=1
> Password: 
> Paste slatepack:
> BEGINSLATEPACK. 3pDmAZBPAaFKxhX Hhi1beNF3pCpmpY ugZNstfhxHzQtrZ zA9HUtMTgbXmUa6 FHQAqRSa3U1fwbu D3iaiYSPLT1hjTE qGMm2rdsVyBofM6 cp6ZDe7Lm3bEm2b 7jmdrzGyfPSTNrL fWrceZbM7rKFo59 bST38KxMXginKca Y7JcQbrJoETKc2W WY6vNTWzfg9QJBt PyDUZhzmMP9KYWT ECjhaagFWtxxfKw pTPMUxgQX6kdbGx NnfuJavCv658VAR ka9upRnBD3ti5MP 27iXnvFYZEpgHJc 4UQF4PutVPdBt2r pXTQ3dRx4bAmDAk j4RG9Y4wMv2h5sc XTKHJP8pHVZGk9n vqeYQWNEK5reqUX rtK4oyA63wCmq9D r75BTjwPn9vdqma eeb9oazDpALNDCn XtguxrSwoPn7coM iCUdCvGKeigZ3rw SokXdb7x8L6x7Ej 3QimTEkg9DoJFe6 FJsEGG5dFQMfzBK 9nEHGvaLt5c2MT3 MBd1FMi9p1fMGmm r7B7bNCMMqpZm6c 7Vfc4F7T4AFRyvF WFbgzGJsafYvfNq oLfZ4vfBquVBaW3 DFsKRBMXnvaA1xy n2L1MqziRyEzGSU BRtmt4xeU3jFtZY HnhsdryC5TdiTV3 i1G6pN6mhJdCXvW nbc51S4HV4gspJJ 3Tw7k2GTt8B4hHC 4Ms93g93PkA2SDZ P19zYouaeerg6iT ScxPXuiZXbC2pZ. ENDSLATEPACK.
> Wallet command failed: LibWallet Error: Sender address has not been provided
> \`\`\`
> 
> Same if you use \`--encrypt-for=\`:
> \`\`\`
> ./grin-wallet --testnet contract sign --receive=1 --encrypt-for=tgrin1wvcfnnsf63qj27yfumukrte7nyyszndcnl4d36crg0yk0dftct3qur8d4t
> Password: 
> Paste slatepack:
> BEGINSLATEPACK. 3pDmAZBPAaFKxhX Hhi1beNF3pCpmpY ugZNstfhxHzQtrZ zA9HUtMTgbXmUa6 FHQAqRSa3U1fwbu D3iaiYSPLT1hjTE qGMm2rdsVyBofM6 cp6ZDe7Lm3bEm2b 7jmdrzGyfPSTNrL fWrceZbM7rKFo59 bST38KxMXginKca Y7JcQbrJoETKc2W WY6vNTWzfg9QJBt PyDUZhzmMP9KYWT ECjhaagFWtxxfKw pTPMUxgQX6kdbGx NnfuJavCv658VAR ka9upRnBD3ti5MP 27iXnvFYZEpgHJc 4UQF4PutVPdBt2r pXTQ3dRx4bAmDAk j4RG9Y4wMv2h5sc XTKHJP8pHVZGk9n vqeYQWNEK5reqUX rtK4oyA63wCmq9D r75BTjwPn9vdqma eeb9oazDpALNDCn XtguxrSwoPn7coM iCUdCvGKeigZ3rw SokXdb7x8L6x7Ej 3QimTEkg9DoJFe6 FJsEGG5dFQMfzBK 9nEHGvaLt5c2MT3 MBd1FMi9p1fMGmm r7B7bNCMMqpZm6c 7Vfc4F7T4AFRyvF WFbgzGJsafYvfNq oLfZ4vfBquVBaW3 DFsKRBMXnvaA1xy n2L1MqziRyEzGSU BRtmt4xeU3jFtZY HnhsdryC5TdiTV3 i1G6pN6mhJdCXvW nbc51S4HV4gspJJ 3Tw7k2GTt8B4hHC 4Ms93g93PkA2SDZ P19zYouaeerg6iT ScxPXuiZXbC2pZ. ENDSLATEPACK.
> Wallet command failed: LibWallet Error: Sender address has not been provided
> \`\`\`

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/grin/original/2X/f/f48d0cbc411b1c1c98092ae5b0fd76cc2650314f.jpeg)

---

<div class="post-metadata">

### Author: ![bruges](https://avatars.discourse-cdn.com/v4/letter/b/b3f665/32.png) [@bruges](https://forum.grin.mw/u/bruges)
#### Post date: [March 8, 2025, 12:45pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/63 "2025-03-08T12:45:59Z")

</div>

I didn’t know that was ready for testing. From the comments I read on github I had a feeling that more work is needed.

Since it’s in grin-wallet, I will try to test it when have time. No need to wait for Grim integration.

---

<div class="post-metadata">

### Author: ![bruges](https://avatars.discourse-cdn.com/v4/letter/b/b3f665/32.png) [@bruges](https://forum.grin.mw/u/bruges)
#### Post date: [March 8, 2025, 12:48pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/64 "2025-03-08T12:48:21Z")

</div>

As I understand contracts and early proofs can be tested independently? But yes, contracts flow has issues, as you pointed.

---

<div class="post-metadata">

### Author: ![Yeastplume](https://avatars.discourse-cdn.com/v4/letter/y/71c47a/32.png) [@Yeastplume](https://forum.grin.mw/u/Yeastplume)
#### Post date: [March 8, 2025, 12:51pm UTC](https://forum.grin.mw/t/grin-product-wishlist/9704/65 "2025-03-08T12:51:33Z")

</div>

Thanks for pointing this out, happy to look this in the near future.

[Previous page](https://forum.grin.mw/t/grin-product-wishlist/9704.md?page=2)

[Next page](https://forum.grin.mw/t/grin-product-wishlist/9704.md?page=4)
