bitrequest / bitrequest.github.io Goto Github PK

What are the possibilities to add Groestlcoin?

Typing the amount for a money request on PC (Windows 11, Microsoft Edge) using the numpad numbers on the keyboard doesn't work.
Using the numbers on the top of the keyboard works.

This is in the context of using Bitrequest for an XMR physical point of sale solution.

There is no way to delete an address, from what I can see. Only an option for '+ Add address' and then the ability to untick the old address. Not a big deal in practice, but removing incorrect addresses is helpful to avoid possible mistakes (esp when app is shared among rotating staff).

If you have two requests for the same price (in crypto) at the same time, will both transactions go through after just 1 payment on the blockchain?

Also, is there a way to validate server-side that a transaction really did go through, and not just that the client sent a malicious API request saying the transaction was done?

This is in the context of using Bitrequest for an XMR physical point of sale solution.

After experimenting, I figured out that tapping outside of the QR code window and bringing it up again does generate a new integrated address. However, what I imagine would be ideal is to have two buttons instead: 'save and new' + 'discard and new'. The 'save and new' would list the invoice under Requests and mark as paid once detected. This means the cashier doesn't have to stand around for 30 sec and wait for the txn to be detected before moving on to the next customer (or start preparing the product).

The closest way to currently emulate what a 'save and new' button would do is to fake share the invoice, which then seems to save it to the Requests page, after which you then open a new request window.

Noticed you're using main addresses for the monero integration.

Due to this, your application is limited in it's ability to have multiple requests open at one time, because you don't want to confuse requests with one another.

Using integrated addresses should help identify the incoming transaction to a specific request, thus allowing you to have multiple requests open at one time.

Really like this project, in that you are compatible with so many chains

Please get the android app into the Fdroid app store for degoogled android users.

This is in the context of using Bitrequest for an XMR physical point of sale solution.

Even better if the description is also then encoded in the QR code so that the sender's wallet picks it up. Flipping back and forth to edit this for every txn is not ideal when trying to quickly serve customers.

It appears when the dialog launches that both horizontal and vertical scrollbars are shown. Is this an easy fix?

Is it as simple as adding this CSS?

#payment {
  overflow: hidden;
}

This is in the context of using Bitrequest for an XMR physical point of sale solution.

Card machines work this way to save time since it is common for values to contain cents. For a $25.95 order, the cashier should just have to enter [2] [5] [9] [5], or for a $5 order [5] [0] [0]. I have observed that it throws cashiers a bit off when they use Bitrequest.

I was just testing out the browser web app and noticed that it would sometimes bring up this window without any user input. The window displayed before this is the QR code window with an amount filled. Refreshing the browser page doesn't solve it (as in, it reoccurs). Not sure under which circumstances this window is supposed to come up or what its purpose is. Seems to take about 10-15 seconds for it to come up after opening the QR window or refreshing the page.

Are there any plans to support banano currency? Super low priority, but would be fun: https://banano.cc/

I am looking for the source-code of io.bitrequest.app on google-play
https://play.google.com/store/apps/details?id=io.bitrequest.app

to test for reproducible-builds as part of walletscrutiny project https://walletscrutiny.com/

this repo looked like close-match, but looks like it only contain code for the web app and not for the mobile apps

please publish the code for android app io.bitrequest.app as well with build instructions on how to build it

This is in the context of using Bitrequest for an XMR physical point of sale solution.

iPads are usually used in landscape mode, which narrows the screen space when the keyboard is displayed. It would be nice if the layout were optimised to allow the request window to fit into the screen space above the keyboard. Currently the usage is quite clumsy in practice. Cashier opens request window, but keyboard then obscures amount field. So, they scroll up to see that they are entering the amount correctly, but this then obscures the QR code. So, they have to close the keyboard to display the QR for scanning. Rinse and repeat for next customer.

I noticed that the request window shows a rounded amount:

The raw amount that actually gets requested in the QR code is 0.446323.

I'm concerned if a user is manually making a payment (rather than scanning the QR code / clicking the open in wallet button), then they will send slightly the wrong amount and the payment will fail in exact mode.

Would you be happy with a PR to show the number of digits that are non-zero?

For context, integrated addresses were active when this error occurred. View key was added with address setup. Using web app, with defaults.

Steps:

1. Produce request and pay amount, which is detected correctly and then stored under Requests.
2. When opening new request window, error pops up "Error: Invalid Viewkey".
3. Payment of this second request is now NOT detected.

No change was made to the wallet. I also cannot see any way to look at or change the view key associated with an address after it has been added the first time.

This is in the context of using Bitrequest for an XMR physical point of sale solution.

Amount is still detected accurately by wallet, just not address. Bitrequest was not set to use integrated address in this instance, and the view key was not added to allow payment detection. It occurred to me that I should have taken a picture of the QR code for troubleshooting. I know this is not very helpful until I can provide an example, sorry. I will add an update here when the error comes up again.

Steps were:

1. Open request window
2. Customer scans and pays successfully (amount and address correct)
3. App is minimised (iOS tablet)
4. App is opened for next customer, amount amended for new order
5. QR code scanned shows 'invalid address' in multiple wallets tested, but still fills amount correctly
6. App must be rebooted to fix