mirror of
https://github.com/monero-project/monero-gui.git
synced 2026-04-19 19:17:27 -04:00
Rename "blackball" for clarity
Apparently some people seem to think it's a censorship list...
This commit is contained in:
moneromooo-monero
@@ -1325,7 +1325,7 @@ The old wallet cache file will be renamed and can be restored later.
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="119"/>
|
||||
<location filename="../pages/SharedRingDB.qml" line="121"/>
|
||||
<source>Blackballed outputs</source>
|
||||
<source>Outputs marked as spent</source>
|
||||
<translation>Blackball'd outputs!</translation>
|
||||
</message>
|
||||
<message>
|
||||
@@ -1336,8 +1336,8 @@ The old wallet cache file will be renamed and can be restored later.
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="122"/>
|
||||
<source>In order to obscure which inputs in a Monero transaction are being spent, a third party should not be able to tell which inputs in a ring are already known to be spent. Being able to do so would weaken the protection afforded by ring signatures. If all but one of the inputs are known to be already spent, then the input being actually spent becomes apparent, thereby nullifying the effect of ring signatures, one of the three main layers of privacy protection Monero uses.<br>To help transactions avoid those inputs, a list of known spent ones can be used to avoid using them in new transactions. Such a list is maintained by the Monero project and is available on the getmonero.org website, and you can import this list here.<br>Alternatively, you can scan the blockchain (and the blockchain of key-reusing Monero clones) yourself using the monero-blockchain-blackball tool to create a list of known spent outputs.<br></source>
|
||||
<translation>In ord'r to be obscurin' which inputs in a XM-ARGHHH transact'on are bein' spent, a third party shant be abl' to dig'st which inputs in thee ring argh already be known to be spent. Bein' abl' to do so would be weakenin' thee protect'on afford'd by ring signat'res. If all but one o' thee inputs are known to be already spent, then thee input bein' actually spent becomes appar'nt, thereby nullifyin' thee effect o' thee ring signat'res, one o' thee three main lay'rs o' privacy protecti'n XM-ARGHHH uses.<br>To help ye transactions to be avoidin' those inputs, a list o' known spent ones can be us'd to avoid usin' them in new transact'ons. Such a list be maintain'd by thee Monero project and be availabl' on thee getmonero.org website, and ye can be importin' t'is list 'ere.<br>Alternativ'ly, ye can be scannin' thee blockchain (and thee blockchain o' the key-reusin' Monero clones) yaself usin' thee monero-blockchain-blackball tool an be creatin' a list o' known spent outputs.<br></translation>
|
||||
<source>In order to obscure which inputs in a Monero transaction are being spent, a third party should not be able to tell which inputs in a ring are already known to be spent. Being able to do so would weaken the protection afforded by ring signatures. If all but one of the inputs are known to be already spent, then the input being actually spent becomes apparent, thereby nullifying the effect of ring signatures, one of the three main layers of privacy protection Monero uses.<br>To help transactions avoid those inputs, a list of known spent ones can be used to avoid using them in new transactions. Such a list is maintained by the Monero project and is available on the getmonero.org website, and you can import this list here.<br>Alternatively, you can scan the blockchain (and the blockchain of key-reusing Monero clones) yourself using the monero-blockchain-mark-spent-outputs tool to create a list of known spent outputs.<br></source>
|
||||
<translation>In ord'r to be obscurin' which inputs in a XM-ARGHHH transact'on are bein' spent, a third party shant be abl' to dig'st which inputs in thee ring argh already be known to be spent. Bein' abl' to do so would be weakenin' thee protect'on afford'd by ring signat'res. If all but one o' thee inputs are known to be already spent, then thee input bein' actually spent becomes appar'nt, thereby nullifyin' thee effect o' thee ring signat'res, one o' thee three main lay'rs o' privacy protecti'n XM-ARGHHH uses.<br>To help ye transactions to be avoidin' those inputs, a list o' known spent ones can be us'd to avoid usin' them in new transact'ons. Such a list be maintain'd by thee Monero project and be availabl' on thee getmonero.org website, and ye can be importin' t'is list 'ere.<br>Alternativ'ly, ye can be scannin' thee blockchain (and thee blockchain o' the key-reusin' Monero clones) yaself usin' thee monero-blockchain-mark-spent-outputs tool an be creatin' a list o' known spent outputs.<br></translation>
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="143"/>
|
||||
@@ -1351,7 +1351,7 @@ The old wallet cache file will be renamed and can be restored later.
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="156"/>
|
||||
<source>Please choose a file to load blackballed outputs from</source>
|
||||
<source>Please choose a file from which to load outputs to mark as spent</source>
|
||||
<translation>Ye best be choosin' a file to load blackball'd outputs from!</translation>
|
||||
</message>
|
||||
<message>
|
||||
@@ -1361,7 +1361,7 @@ The old wallet cache file will be renamed and can be restored later.
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="174"/>
|
||||
<source>Filename with outputs to blackball</source>
|
||||
<source>Filename with outputs to mark as spent/unspent</source>
|
||||
<translation>Filename wit' outputs to thee blackb'll</translation>
|
||||
</message>
|
||||
<message>
|
||||
@@ -1376,7 +1376,7 @@ The old wallet cache file will be renamed and can be restored later.
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="214"/>
|
||||
<source>Or manually blackball/unblackball a single output:</source>
|
||||
<source>Or manually mark a single output as spent/unspent:</source>
|
||||
<translation>Or manual'y blackb'll/unblackball a single output:</translation>
|
||||
</message>
|
||||
<message>
|
||||
@@ -1391,12 +1391,12 @@ The old wallet cache file will be renamed and can be restored later.
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="238"/>
|
||||
<source>Blackball</source>
|
||||
<source>Mark as spent</source>
|
||||
<translation>Blackball!</translation>
|
||||
</message>
|
||||
<message>
|
||||
<location filename="../pages/SharedRingDB.qml" line="247"/>
|
||||
<source>Unblackball</source>
|
||||
<source>Mark as unspent</source>
|
||||
<translation>Unblackball!</translation>
|
||||
</message>
|
||||
<message>
|
||||
|
||||
Reference in New Issue
Block a user