View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011604 | Taler | deploymerizer | public | 2026-07-03 08:21 | 2026-08-09 22:51 |
| Reporter | Antoine A | Assigned To | Antoine A | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0011604: New burn address design | ||||
| Description | bitcoin-depolymerize only support reserve incoming transaction. We need to add both KYC and MAP support. With new taprot address design we can send up to 40 bytes that is enough for key + prefix making small subject unnecessary. I suggest: RES + 32B key MAP + 32B key KYC + 32B key If such addresses are not accepted we could use derived address of 32B using Taproot P2TR addresses. Having only one additional address to send to will make the user experience much better | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-07-03 08:21 | Antoine A | New Issue | |
| 2026-07-03 08:21 | Antoine A | Status | new => assigned |
| 2026-07-03 08:21 | Antoine A | Assigned To | => Antoine A |
| 2026-07-03 08:24 | Antoine A | Description Updated | |
| 2026-08-09 22:51 | Christian Grothoff | Target Version | 1.7 => post-1.0 |
| 2026-08-09 22:51 | Christian Grothoff | Status | assigned => implementing |