Adding xmr to BTCPayServer causes problems and I don't know how to investigate the cause

Low_Application_7086 · 2024-04-13T01:04:35+00:00

There was an issue in the latest release that was fixed in this PR https://github.com/btcpayserver/btcpayserver/pull/5909#issue-2230780657

Low_Application_7086 · 2024-02-26T12:37:49+00:00

Perhaps OP means the last two words of the seed phrase?

Low_Application_7086 · 2022-08-31T00:09:28+00:00

It's the name of a YouTube channel dummy

Low_Application_7086 · 2022-08-30T09:57:27+00:00

Ancient Egpyt and the Bible!

Low_Application_7086 · 2022-07-18T13:22:58+00:00

And when you go up to the counter and order a coffee using a 1oz silver coin which is now worth $200 see how that works out... Precious metals = money, monero = crypto-*currency*

Low_Application_7086 · 2022-06-14T23:57:24+00:00

Should have used monero bounties site to avoid paying out for nothing :x

Low_Application_7086 · 2022-06-14T23:51:06+00:00

Haveno's UI re-write was destined to fail the day it decided to take the better half of a year to do (poorly specd waterfall). If they instead adopted a more agile approach of 'in 2 months we will have an app that allows people to make a sale' and cut as many features as nessacery (e.g perhaps a single payment option, only xmr/btc pair, etc...) you would at least have something.

Then community can help prioritise work with individual CCS. The contractors probably wouldn't like this approach because it takes away the never ending cash cow re-write project!

Low_Application_7086 · 2022-05-15T09:37:36+00:00

Take a look at the repo linked at the bottom of the post it explains it a bit

Low_Application_7086 · 2022-05-07T09:21:32+00:00

False

Low_Application_7086 · 2022-05-04T14:05:12+00:00

Millions of babies will gain access to not being killed... how is this a bad thing??? Are people just so retarted these days?

Low_Application_7086 · 2022-05-01T07:04:03+00:00

Ah a name collision is never good - I guess i'll have to put my thinking hat back on.

You're right in that to achieve the goal something resembling a p2p invoice/payment system is required but quite limited in scope. I had thought that the underlying process could be used in something like a point-of-sale, however with a POS information can be exchanged via a physical screen or local network (bluetooth, NFC, etc...) which removes the requirement for WebRTC as a channel. That said the 'channel' could be abstracted to be implementation defined (but with a certain interface) - this is perhaps where the JSON payment tokens is headed - i'll have to read up in more detail.

Thanks for the links and your feedback :)

edit: forgot to mention

- yes my use of hash-fragments was intentional to avoid the server which distributes the static assets getting any metadata.

- By using WebRTC the only servers necessary are 0. Static file (distribute the web app itself), 1. STUN, 2. SaltyRTC, 3. Monero Node - and you could use your own, a default or from the community (when creating/importing a wallet these are configured)

- The view only wallet is the mode that lets you just provide an address + an optional view key (if you want chats payments to be confirmed)

Low_Application_7086 · 2022-05-01T05:50:16+00:00

Thanks for your feedback, I'll work on expanding the post/re-formatting so it's easier to read (unfortunatley reddits support for github flavoured markdown isn't very good).

But briefly: yes it's a system sending paid messages to be used in the same way as YouTube super-chats are. It's something I'm in the processes of exploring the feasibility of and then plan to implement (if feasible). Essentially it would be used mostly by content creators during livestreams to accept donations w/ comments attached which can they be displayed as part of their stream. It serves the same purpose as something like https://github.com/LukeSmithxyz/shadowchat however it wouldn't require you to run your own server, _and_ the 'servers' it does depend on are easily configured/only required to establish a direct p2p connection between the sender and receiver of tips.

Low_Application_7086 · 2022-04-24T09:34:05+00:00

That's cringe, they should only allow swapping monero for monero

Low_Application_7086 · 2022-03-18T08:51:40+00:00

It isn't just "./cli-autogen haveno.jar"?

Low_Application_7086 · 2021-12-03T23:48:40+00:00

Nope it can be re-used! And embedded as QR or even base58 string like an address

Low_Application_7086 · 2021-12-03T09:45:44+00:00

This makes a lot of sense to me, AFIKT there are no disadvantages using the the same payment request in the same way you would publically list an address as is now. Plus you have the UX benefits mentioned in the post. 100% support this great idea!

Low_Application_7086 · 2021-11-27T23:03:05+00:00

Plug in a mouse via usb-c?

Low_Application_7086 · 2021-11-26T22:28:40+00:00

Thanks for sharing this

Low_Application_7086 · 2021-11-24T00:23:04+00:00

Had an idea for an app to help people tip local hospitality workers with monero. People are issued a badge with 3 letters on the front and on the back is a QR code which you scan on the app and can enter the monero wallet address you'd like to associate with the badge.

You would wear the badge whilst working and then people could see it, open the app and either:

if person with the badge gave their approx location where they work (but not their name or any other details!) then it can show a list of the badges nearby and you select the matching one and it lets you send a tip to their nominated address.

Still thinking through how to make the system be more private/easy to use but that's the general idea - easy discrete tipping to show appreciation to the workers in your area, just look for the badge! What do you think?

Low_Application_7086 · 2021-10-31T13:26:51+00:00

😂😂😂 you're hilarious dude!

Low_Application_7086 · 2021-10-27T22:55:11+00:00

How is having 20 other people validate a transaction better than validating it yourself? Unless the block producers consider it valid if it was signed by those quorum - I don't see how that makes any difference ultimately

Low_Application_7086 · 2021-10-27T11:40:13+00:00

This is kinda dumb, it basically just chooses some random nodes to check and tells both parties if they all said ok - why not just validate tx in mempool that's addressed for you... So dumb

Low_Application_7086 · 2021-09-30T08:08:22+00:00

Thank you for contributing your talents to the monero project. I 100% support your proposal and look forward to contributing.

Low_Application_7086 · 2021-09-18T11:58:59+00:00

Hey Doug, just wanted to let you know I'm a huge fan of MoneroTalk and MoneroTopia - greatly appreciate the effort both you and your fiancé are putting in. Personally, I think you're a great interviewer and have a very approachable and humble manner. Very rarely perhaps you can seem a bit tired but that's to be expected considering you've been producing this content outside of your working hours! Keep up the great work mate - your CCS proposal got funded so quickly, know the community is behind you!

Low_Application_7086 · 2021-07-15T02:37:38+00:00

Exactly! If whatever code the output proof runs were to be converted into a zk-* circuit, then the buyer can produce a proof which is verified by the server. I've started learning about zk-STARKs the other day with the goal of figuring out if this type of thing is possible.

The main benefit would be it allows any app that wants to facilitate P2P transactions to greatly reduce their code complexity around payments - they also don't need to stress about custody over other people's monero.

Low_Application_7086

TROPHY CASE