View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0007494 | Taler | wallet (Android App) | public | 2022-11-25 12:46 | 2023-01-26 22:53 |
Reporter | Christian Grothoff | Assigned To | grote | ||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
Product Version | git (master) | ||||
Target Version | 0.9.1 | Fixed in Version | 0.9.1 | ||
Summary | 0007494: depositing back onto chain for Bitcoin asks for IBAN | ||||
Description | When selecting 'send funds' and then 'to bank account' for a Wallet containing bitcoins, the Android wallet asks for an IBAN and SWIFT code, instead of asking for a bitcoin address. Thus, the bitcoin payto://-method seems to not be properly supported by the current Android wallet, making it impossible to move funds back onto the Bitcoin chain. | ||||
Tags | No tags attached. | ||||
|
Would you mind making the details needed here explicit please? What fields would need to be shown to the user? Instead of IBAN and SWIFT, just a single field for BTC address? should that address get validated somehow? For creating a PaytoUriBitcoin, we currently require a list of segwitAddresses a targetPath and parameters. How do those map to the UI? And then how is the textual payto:// URI created from that? This part is still missing in the code sebastian did. |
|
For wiring funds back to the user's bitcoin wallet, we only need the simple single Bitcoin wallet address. RFC 8905 already gives an example for what the payto:// address would look like: payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu So simply have a text field where the user can enter something like "12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu". Note that Bitcoin addresses have some checksum, which ideally our UIs should validate before accepting the address. |
|
Fixed with ab1f17d3877c065120bedcef30044fe51b8145e3 |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-11-25 12:46 | Christian Grothoff | New Issue | |
2022-11-25 12:46 | Christian Grothoff | Status | new => assigned |
2022-11-25 12:46 | Christian Grothoff | Assigned To | => grote |
2022-12-20 18:26 | Christian Grothoff | Target Version | 0.9.1 => 0.9.2 |
2023-01-03 14:30 | grote | Assigned To | grote => Christian Grothoff |
2023-01-03 14:30 | grote | Status | assigned => feedback |
2023-01-03 14:30 | grote | Note Added: 0019553 | |
2023-01-06 15:07 | Christian Grothoff | Note Added: 0019596 | |
2023-01-06 15:08 | Christian Grothoff | Assigned To | Christian Grothoff => grote |
2023-01-06 17:24 | grote | Status | feedback => resolved |
2023-01-06 17:24 | grote | Resolution | open => fixed |
2023-01-06 17:24 | grote | Note Added: 0019601 | |
2023-01-08 10:10 | Christian Grothoff | Fixed in Version | => 0.9.1 |
2023-01-08 10:10 | Christian Grothoff | Target Version | 0.9.2 => 0.9.1 |
2023-01-26 22:53 | Christian Grothoff | Status | resolved => closed |