Sa coinjoin naman, may minimum amount kang dapat para ma mix mo doon kaso nga lang sobrang taas eh as stated ni maus.
Pero hindi kasama yung minimum amount sa FAQ page nila at base sa "video na ito", 0.001 [roughly $20 sa ngayon] lang ang auto-start coinjoin threshold ng version 2, so hindi siya ganun kataas.
Topic: Wasabi Wallet V2.0 Pinoy Discussion (Read 510 times)
Sa coinjoin naman, may minimum amount kang dapat para ma mix mo doon kaso nga lang sobrang taas eh as stated ni maus.
Pero hindi kasama yung minimum amount sa FAQ page nila at base sa "video na ito", 0.001 [roughly $20 sa ngayon] lang ang auto-start coinjoin threshold ng version 2, so hindi siya ganun kataas. magkano kaya transaction fee ng wasabi? goods to kapag medyo cautious ka sa mga transaction mo and gusto mo retain ang privacy mo.
Merong automatic na calculated na yung fee pero pwede mo pa rin naman iset kung ilang sat/byte ang gusto mo. Kadalasan ginagawa ko lang 10 sats/byte o di kaya hanggang 15 sats/byte para lang mas mabilis yung transaction ko. Pero madalas naman kahit hindi mo na iset eh ok naman at confirmed din naman agad. Sa coinjoin naman, may minimum amount kang dapat para ma mix mo doon kaso nga lang sobrang taas eh as stated ni maus. magkano kaya transaction fee ng wasabi? goods to kapag medyo cautious ka sa mga transaction mo and gusto mo retain ang privacy mo.
Parang katulad lang din yan ng Electrum, pwede mo i-specify kung magkano yung gagamitin mong tx fee gamit yung slider na makikita mo don sa "Send" tab ng wallet. Usually less than a dollar lang yung fee kapag hindi busy yung mempool (waiting room for the transactions). As for the coinjoin, alam ko may additional fee, pero hindi ako sure kung included na siya sa specified tx fee nung nagsend ka ng bitcoin to somewhere else.Quote from: https://www.wasabiwallet.io/faq.html
Coinjoining coins with a value above 0.01 BTC costs 0.3% as a coordinator fee + mining fees. Inputs of 0.01 BTC or below don't pay coordinator fees, nor remixes, even after one transaction. Thus, a payment made with coinjoined funds allows the sender and the recipient to remix their coins without paying any coordinator fees.
magkano kaya transaction fee ng wasabi? goods to kapag medyo cautious ka sa mga transaction mo and gusto mo retain ang privacy mo.
Meron bang malaking pinagkaiba ang Traditional Bitcoin Mixer sa coinjoin ni Wasabi bukod sa pag traditional Bitcoin Mixer, eh as one entity lang na mag mix ng coins mo, while coinjoin will need other coinjoin participants("multi-user")?
May isa pang difference sa kanila [yung centralized coordinator sa Wasabi na kaya niyang ifilter out ang mga UTXOs (not sure kung naimplement na nila ito, pero it defeats its purpose to some extent)].Mga hardware wallet na Officially supported:
~Snipped~
May dalawang nadagdag sa listahan nila [ColdCard MK4 at Trezor Model T]. ~Snipped~
That way, meron mga 2 or 3 hops in betw
This, but I'd go as far as doing 10+ hops para mas sigurado (ok lang maging praning pagdating sa pera/privacy). Fortunately maraming times na sobrang baba ng fees ngayon, so take advantage nalang talaga nung 1-5 sats/b transaction fees.
Meron bang malaking pinagkaiba ang Traditional Bitcoin Mixer sa coinjoin ni Wasabi bukod sa pag traditional Bitcoin Mixer, eh as one entity lang na mag mix ng coins mo, while coinjoin will need other coinjoin participants("multi-user")?
Heto ang isang article na aking natagpuan mula sa post ni nopara73(https://bitcointalksearch.org/topic/m.48383499)
Ang link ng article ay : https://nopara73.medium.com/traditional-bitcoin-mixers-6a092e59d8c2
Itoy estimated na limang minutong basahin pero super worth it,
Heto ang isang article na aking natagpuan mula sa post ni nopara73(https://bitcointalksearch.org/topic/m.48383499)
Ang link ng article ay : https://nopara73.medium.com/traditional-bitcoin-mixers-6a092e59d8c2
Itoy estimated na limang minutong basahin pero super worth it,
Mga listahan ng Officially supported software and hardware ni Wasabi Wallet:
Operating Systems na Officially supported:
Mga hardware wallet na Officially supported:
source: https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-operating-systems
Operating Systems na Officially supported:
- Windows 10 1607+ (except 1703)
- macOs 10.15+
- Ubuntu 16.04, 18.04, 20.04+
- Fedora 33+
- Debian 10+
Mga hardware wallet na Officially supported:
- ColdCard MK1
- ColdCard MK2
- ColdCard MK3
- Ledger Nano S
- Ledger Nano X
source: https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md#officially-supported-operating-systems
- 
-
-
Sa tingin ko, ok naman parin gamitin ang Wasabi, kung ang balak mo is to have medyo clean coins. It's better than using an exchange or a gaming / dice website. Pero since meron sinasabi na nag tracking daw o meron analysis sa Wasabi, kasi nga the default coordinator will use blacklists, eh then baka wag mo muna gamitin.
Para sa akin, kailangan mo lang gumamit ng dalawang wallet. Either your default Bitcoin Core wallet o something like Electrum. Dun mo muna send ang coins mo. Then send mo ulet to another address. Then send mo to your Wasabi wallet. Then send mo to either another address in your own wallet or make a new wallet. That way, meron mga 2 or 3 hops in between.
Then, saka mo lang send sa exchanges o kung saan mo gagamitin. I don't ever store any coins and just leave it in Wasabi.
Para sa akin, kailangan mo lang gumamit ng dalawang wallet. Either your default Bitcoin Core wallet o something like Electrum. Dun mo muna send ang coins mo. Then send mo ulet to another address. Then send mo to your Wasabi wallet. Then send mo to either another address in your own wallet or make a new wallet. That way, meron mga 2 or 3 hops in between.
Then, saka mo lang send sa exchanges o kung saan mo gagamitin. I don't ever store any coins and just leave it in Wasabi.
as at some point every single bitcoin is going to be so-called "dirty" or "tainted" anyway.
except satoshi coins, or those that have been lost or cannot be recovered. etc.,
baka naman po pwedeng paliwanag ng expert dito bakit ilan sa mga prominenteng membro ng bitcointalk ay hindi masaya sa bagong Wasabi Wallet(Wasabi 2.0)?
translation:
May an expert be very kind to explain to us why are some of the prominent members of bitcointalk are not happy with the Wasabi 2.0..?
Terms like:
Blacklist and why
Effects pros and con
...
Thank you in advance masters!
pacorrect na lang po kung mali.
So ayun sa nabasa ko dun sa 24 q and a ni n0nce and wasabi team, medyo madami daw talagang nalilito sa kung ano ung blacklist,
source(https://bitcointalksearch.org/topic/--5286821)
Quote from: icopress link=topic=5286821.msg60514370#msg60514370
Many people seem to struggle understanding what zkSNACKs blacklisting really means and why we are doing it, so let’s start from the basics. ZkSNACKs is a company that sponsors the development of an open-source project called Wasabi Wallet. This company also runs the default coordinator that is needed to create coinjoin transactions in Wasabi. This coordinator service can be run by other entities too, as everything is open and available. Users are able to choose which coordinator they want to communicate with but unfortunately there are not many options, as running one has its risks and not many people are willing to do it.
The zkSNACKs coordinator is clearly the largest and has substantially more liquidity than others; hence, this is why most people use it. Wasabi Wallet was built in a way that the developers and zkSNACKs don't collect any data about their users. We do not care who you are and what you do with your bitcoins! We don't want to know. Unfortunately, some people do collect data, attach it to bitcoin addresses and make decisions based on that information. The company is getting in trouble and harassed because apparently some of the users of our coordinator are so-called “criminals”, according to the people keeping up these databases.
The zkSNACKs coordinator is clearly the largest and has substantially more liquidity than others; hence, this is why most people use it. Wasabi Wallet was built in a way that the developers and zkSNACKs don't collect any data about their users. We do not care who you are and what you do with your bitcoins! We don't want to know. Unfortunately, some people do collect data, attach it to bitcoin addresses and make decisions based on that information. The company is getting in trouble and harassed because apparently some of the users of our coordinator are so-called “criminals”, according to the people keeping up these databases.
So zkSNACKs pa rin ang magseset ng sinong b-blacklist for coinjoin, karapatan naman nila kasi siyempre they have the right to refuse and serve whatever they decide, sa kanila iyon eh. Ang mabblacklist eh di lang naman makakapagcoinjoin, pero pwede pa rin gamitin si wallet to store coins.
Para sa akin maganda nga tong ganito na immake sure ni Wasabi na walang surprise yung coins mo. What I mean by surprise is, walang illegal na data na linked dito. Kunwari ung mga childporn links na nakalink sa coin, kung sakaling kasama ito sa blacklisting category ni zkSNACKs(sana kasama), eh di na madadamay pa sa surprise nang dirty coin na yun yung mga magco-coinjoin.
Sabi naman ng ibang prominent members, panget daw kasi mauusisa pa iyong coin history, meaning maaaring matraceback sa user something something. . . na privacy concern sabi nila.
Nakalimutan mong banggitin na ang mga naturang barya ay karaniwang nagkakahalaga ng 30-40% na higit pa sa halaga ng pamilihan.
Not sure about the numbers but so-called "clean" bitcoin apparently does have price premiums. There's no way I'm paying any premiums though, as at some point every single bitcoin is going to be so-called "dirty" or "tainted" anyway.
Walang way para ma-achieve ito, dahil technically impossible lang talaga since hindi naman nabubura ung history ng BTC transactions. And yes, kung gusto mo ng coins na literally na sayo lang ung "fingerprint", ang paraan lang is ikaw ung magmine nung coins mismo. Or probably maghanap ka ng miner na magbebenta sayo nung coins na wala pang transaction history.
Nakalimutan mong banggitin na ang mga naturang barya ay karaniwang nagkakahalaga ng 30-40% na higit pa sa halaga ng pamilihan.
Wasabi Wallet V2.0.1 Release
So after nga po ng initial release ng Wasabi Wallet V2.0, na nakita nga na maraming vulnerabilities in lieu with network failures for example is yung on going na DDoS attack. The wasabi team is recommending everybody to update to this version.
https://github.com/zkSNACKs/WalletWasabi/releases
Credits to dkbit98 for the this link.
whats changed
So after nga po ng initial release ng Wasabi Wallet V2.0, na nakita nga na maraming vulnerabilities in lieu with network failures for example is yung on going na DDoS attack. The wasabi team is recommending everybody to update to this version.
https://github.com/zkSNACKs/WalletWasabi/releases
Credits to dkbit98 for the this link.
whats changed
Code:
2.0 website by @CAnorbo in #8373
Improve backend log a bit by @adamPetho in #8389
Optimize MaxSuggestedAmount variation by @molnard in #8390
Add Human readable round information API by @molnard in #8391
Fix LegalDocs link in website by @adamPetho in #8392
Keep largest MaxSuggestedAmount until successful input reg by @molnard in #8393
Add log for possible blame failure catch by @nopara73 in #8397
Remove nonimportant tohashsets those might ruin things by @nopara73 in #8401
Log witness count by @nopara73 in #8402
Add more log by @nopara73 in #8403
Add more logs by @nopara73 in #8404
Remove unnecessary log by @nopara73 in #8407
Add wabisabi request statista by @nopara73 in #8410
Increase statista time to 60 minutes by @nopara73 in #8411
[Fix] Registration halt by @lontivero in #8417
If someone didnt confirm fail and blame by @nopara73 in #8418
Add back output reg step for blame rounds by @nopara73 in #8432
Add buffer times by @nopara73 in #8433
Reduce buffer of signing to zero by @nopara73 in #8441
Send NotAllAlicesSign so people get into blame round by @nopara73 in #8442
Revert blame round creation by @nopara73 in #8443
Fix order by @nopara73 in #8444
Add buffer for output reg by @nopara73 in #8445
Timeout fast when previous phase failed by @nopara73 in #8464
Revert buffer time by @nopara73 in #8465
Fix unit test by @nopara73 in #8466
Never release during a Tor network disruption by @nopara73 in #8431
TorHttpPool: Split lock to allow concurrent Tor circuits creation [dev 2.0.1] by @kiminuo in #8469
Decrease input reg available time, so the clients hurry up. by @adamPetho in #8472
Chaos monkey by @lontivero in #8468
Add phase to human monitor and order results by importance by @nopara73 in #8485
Log phase duration in case of late requests, so we can analyze it by @adamPetho in #8471
Implement parallel rounds by @nopara73 in #8486
Implement WW2.0.0 Compatible CJ Load Balancer by @nopara73 in #8495
Improve DDoS Protection by @nopara73 in #8499
TorMonitor: Verify using software-versions API [dev 2.0.1] by @kiminuo in #8481
Update Tor to 0.4.7.7 [dev 2.0.1] by @kiminuo in #8475
Abort pending requests when we are late by @lontivero in #8489
Continue retrying requests until the phase finishes by @lontivero in #8504
Upgrade xUnit to get NRT support by @kiminuo in #8507
Load Balancing by @nopara73 in #8506
.editorconfig: Insert final newline to all files by @kiminuo in #8509
Do not unregister wrong phase by @lontivero in #8493
Try fix tokens around registration by @nopara73 in #8512
Add missing EndRoundState msgs by @nopara73 in #8510
[trivial] Fix analyzer error. by @kiminuo in #8474
[VDG] Add Tor Status Checker by @SuperJMN in #8476
Clarify wording + Increase Time by @nopara73 in #8524
Drop exit node after 2h instead of 1d by @nopara73 in #8525
Antifragility Pack WW2.0.1 by @nopara73 in #8497
Cancel when not conn conf by @nopara73 in #8520
Make WW2.0.0 client most preferred round to be the last by @nopara73 in #8521
Avoid exit nodes by @nopara73 in #8533
trivial - typo fix by @MarnixCroes in #8532
Fix for Tor Checker preventing application from closing normally by @SuperJMN in #8534
[VDG] Make TorIssuesControl have a proper size in StatusIcon by @SuperJMN in #8539
IHttpClient: Add missing OperationCanceledException by @kiminuo in #8545
Use PeriodicRunner for Tor Status Checker by @SuperJMN in #8536
Revert fallback removal by @nopara73 in #8551
Keep retrying for any transport exception by @nopara73 in #8542
Firefox blur effect fixes by @CAnorbo in #8552
2.0.1 download links by @CAnorbo in #8554
Update version to 2.0.1 by @molnard in #8555
Improve backend log a bit by @adamPetho in #8389
Optimize MaxSuggestedAmount variation by @molnard in #8390
Add Human readable round information API by @molnard in #8391
Fix LegalDocs link in website by @adamPetho in #8392
Keep largest MaxSuggestedAmount until successful input reg by @molnard in #8393
Add log for possible blame failure catch by @nopara73 in #8397
Remove nonimportant tohashsets those might ruin things by @nopara73 in #8401
Log witness count by @nopara73 in #8402
Add more log by @nopara73 in #8403
Add more logs by @nopara73 in #8404
Remove unnecessary log by @nopara73 in #8407
Add wabisabi request statista by @nopara73 in #8410
Increase statista time to 60 minutes by @nopara73 in #8411
[Fix] Registration halt by @lontivero in #8417
If someone didnt confirm fail and blame by @nopara73 in #8418
Add back output reg step for blame rounds by @nopara73 in #8432
Add buffer times by @nopara73 in #8433
Reduce buffer of signing to zero by @nopara73 in #8441
Send NotAllAlicesSign so people get into blame round by @nopara73 in #8442
Revert blame round creation by @nopara73 in #8443
Fix order by @nopara73 in #8444
Add buffer for output reg by @nopara73 in #8445
Timeout fast when previous phase failed by @nopara73 in #8464
Revert buffer time by @nopara73 in #8465
Fix unit test by @nopara73 in #8466
Never release during a Tor network disruption by @nopara73 in #8431
TorHttpPool: Split lock to allow concurrent Tor circuits creation [dev 2.0.1] by @kiminuo in #8469
Decrease input reg available time, so the clients hurry up. by @adamPetho in #8472
Chaos monkey by @lontivero in #8468
Add phase to human monitor and order results by importance by @nopara73 in #8485
Log phase duration in case of late requests, so we can analyze it by @adamPetho in #8471
Implement parallel rounds by @nopara73 in #8486
Implement WW2.0.0 Compatible CJ Load Balancer by @nopara73 in #8495
Improve DDoS Protection by @nopara73 in #8499
TorMonitor: Verify using software-versions API [dev 2.0.1] by @kiminuo in #8481
Update Tor to 0.4.7.7 [dev 2.0.1] by @kiminuo in #8475
Abort pending requests when we are late by @lontivero in #8489
Continue retrying requests until the phase finishes by @lontivero in #8504
Upgrade xUnit to get NRT support by @kiminuo in #8507
Load Balancing by @nopara73 in #8506
.editorconfig: Insert final newline to all files by @kiminuo in #8509
Do not unregister wrong phase by @lontivero in #8493
Try fix tokens around registration by @nopara73 in #8512
Add missing EndRoundState msgs by @nopara73 in #8510
[trivial] Fix analyzer error. by @kiminuo in #8474
[VDG] Add Tor Status Checker by @SuperJMN in #8476
Clarify wording + Increase Time by @nopara73 in #8524
Drop exit node after 2h instead of 1d by @nopara73 in #8525
Antifragility Pack WW2.0.1 by @nopara73 in #8497
Cancel when not conn conf by @nopara73 in #8520
Make WW2.0.0 client most preferred round to be the last by @nopara73 in #8521
Avoid exit nodes by @nopara73 in #8533
trivial - typo fix by @MarnixCroes in #8532
Fix for Tor Checker preventing application from closing normally by @SuperJMN in #8534
[VDG] Make TorIssuesControl have a proper size in StatusIcon by @SuperJMN in #8539
IHttpClient: Add missing OperationCanceledException by @kiminuo in #8545
Use PeriodicRunner for Tor Status Checker by @SuperJMN in #8536
Revert fallback removal by @nopara73 in #8551
Keep retrying for any transport exception by @nopara73 in #8542
Firefox blur effect fixes by @CAnorbo in #8552
2.0.1 download links by @CAnorbo in #8554
Update version to 2.0.1 by @molnard in #8555
So possible ba na kung iyong Coins na pinambayad sayo is once used in a "dirty/illegal transaction" na wala ka namang kinalaman eh tanggihan para masali sa CoinJoin?
Unfortunately, malaki ang possibility na mangyari ito at considering na "nag hire sila ng analysis company" para iextract ang certain inputs, I wouldn't be surprised to see them go 10 levels deep [sa ibang salita, most likely magkakaroon ng collateral damages in the process].Iyon lang. Isa itong malaking pag atake sa privacy ng mga previous transactions. At kung 10 levels deep ang gagawin ng analysis company na kanilang ihihire, posibleng kahit tayo na di naman gumagawa ng something illegal with our coins ay matamaan dahil sa lalim ng iaanalyse. Ito pala iyong hinihimutok ng karamihan ng sa discussions.
So possible ba na kung iyong Coins na pinambayad sayo is once used in a "dirty/illegal transaction" na wala ka namang kinalaman eh tanggihan para masali sa CoinJoin?
Unfortunately, malaki ang possibility na mangyari ito at considering na "nag hire sila ng analysis company" para iextract ang certain inputs, I wouldn't be surprised to see them go 10 levels deep [sa ibang salita, most likely magkakaroon ng collateral damages in the process]. Ang tanong ano itong coordinator na ito. Ito yata iyong ayaw ng mga Chipmixer folks na nagdidiscuss dito.
Limited din ang knowledge ko tungkol dyan pero sa tingin ko tama ka... Isa itong "centralized coordinator" na kaya niyang "tanggihan ang mga UTXOs" from being a part of the coinjoin process.- The following thread might also come in handy: The default Wasabi Wallet coordinator will start censoring "illegal" UTXOs
As far as I know, yes mining lang ang way para makakuha ng "non-fingerprint" BTC because of proof of work mechanism niya.
Or find a miner who's willing to sell the private key of an address that cointains only newly generated coins.- Personally, I don't think it's worth the trouble to pay a ridiculous amount for those.
Ang pagkakaintindi ko is this Coordinator will have the ability to determine a "dirty bitcoin", so possible na di isasama sa Coinjoin process itong mga coins na ito. Tapos dun sa link na shinare mo SFR10, sabi possibly daw na itong coordinator na ito ay mag iinvade na privacy ng mga tao, siyempre pano nila madedetermine iyong "dirty bitcoins" kung hindi gagawa ng thorough analysis ito.
So possible ba na kung iyong Coins na pinambayad sayo is once used in a "dirty/illegal transaction" na wala ka namang kinalaman eh tanggihan para masali sa CoinJoin?
Ang tanong ano itong coordinator na ito. Ito yata iyong ayaw ng mga Chipmixer folks na nagdidiscuss dito.
Limited din ang knowledge ko tungkol dyan pero sa tingin ko tama ka... Isa itong "centralized coordinator" na kaya niyang "tanggihan ang mga UTXOs" from being a part of the coinjoin process.- The following thread might also come in handy: The default Wasabi Wallet coordinator will start censoring "illegal" UTXOs
As far as I know, yes mining lang ang way para makakuha ng "non-fingerprint" BTC because of proof of work mechanism niya.
Or find a miner who's willing to sell the private key of an address that cointains only newly generated coins.- Personally, I don't think it's worth the trouble to pay a ridiculous amount for those.
As far as I know, yes mining lang ang way para makakuha ng "non-fingerprint" BTC because of proof of work mechanism niya. Medyo nalilito ako dun sa part ng miner na magbebenta ng coins na wala pang transaction history, Do you mean mag benta ng wallet na ginamit sa pag mine ng BTC? Kasi I think na once sinend ng miner yung BTC to other wallet address is may history na agad siya sa blockchain.
Yes obviously magkakaroon ng transaction history pag sinend na. Pero ang point is wala pang transaction history from other entities na pwedeng mag-cause ng suspicion sa kahit anomang bagay dahil miner->you transaction lang ung history.
Jump to: