they could do like what mutiny wallet does and run most of the node in the browser, and for the rest use a web based proxy

Ok um...someone made an allegation so you did the "responsible" thing and erased the software you enjoyed? What if I make an allegation that linux is controlled by the wef, are you gonna erase your operating system too? If I allege that the golden gate bridge was funded by the wef are you gonna be "responsible" and jump off it? Seems like a pretty easy way to control you, I'll just watch for whenever you do something I don't like and then I'll allege that the wef wants you to do that

Maybe the next time someone alleges the wef is behind some piece of software you like you'll think twice before uninstalling it. Do a little independent thinking is my recommendation and don't just believe random allegations you find on the internet

There are two easy ways to control someone: if you find out they always do whatever you say, tell them to do X, and watch them do it. And if you find out they always do the opposite, just tell them not to do X, then watch them do it.

perhaps they appreciate the information about the kickout protocol even though it addresses something else

I talked with some folks about sybil resistance after making that post and it looks like the two main sybil resistance methods are:

Of the two models I think the first one is easier to implement (I can just increase the mining fee parameter) but I prefer the second option

I love stuff like this! Going through this tutorial would make an excellent workshop for a bitdevs or similar, and it would also be great to present at a bitcoin conference

Emessbee also requires users to pay for their own block space. The mining fee is calculated after all change addresses are submitted, then divided up equally among all participants, and deducted from the amount that would otherwise go to users as change

oh, I didn't realize that

oops

oh

oops

I took a lot of inspiration from joinmarket, which is the only coinjoin software I've ever used (other than testing my own). But I think I found a better way to banish sybils aka trolls, though I haven't yet implemented it.

Suppose in round 1, 100 people register for a coinjoin. If a troll never enters this round, no harm is done. If a troll sends a registration message for this round, there are three ways he can do it incorrectly: not register a valid change output, not register 1 or 2 valid inputs, or register 1 or 2 valid inputs but without proving ownership (you're supposed to sign a recent blockhash with the inputs' private keys). All of those are publicly detectable by every participant, so everyone simply ignores messages that fail any of these steps, and thus every honest participant continues to round 2 with the same set of other honest people. In other words, trollish "Round 1" messages are discarded by all honest parties, so they have no effect, it is as if the trolls never sent a message and thus never entered Round 1.

Suppose the trolls did round 1 correctly and are now in round 2. There are three ways a troll can do round 2 incorrectly: not register a valid "equal amount" output, register "too many" equal amount ouputs, or not provide a valid ring signature proving they were in round 1. All honest parties discard messages that lack valid ring signatures, so that part has no effect, it is as if they never sent the message. To detect a troll who uses either of the other two trollish behaviors (i.e. they register 0 or more than 1 "equal amount" output), all parties sum up the number of equal amount outputs and, if it is not equal to the number of people who were in round 1, they know a troll is among them. Therefore, every honest participant should send a new message to the group that unmasks their ring signature, thus revealing which of their inputs map to which of their outputs. If anyone does not do this, or if their now-mapped signature demonstrates that they submitted multiple outputs, the honest participants have identified a troll and the troll's inputs (they are whichever inputs were in a "round 1" message whose "ringsig pubkey" has not been unmasked as "belonging to" one of the outputs), so they kick that troll's inputs out of the group and restart with the remaining honest people. Continue this procedure until you enter round 3 or you are the only coinjoiner left, which just means there were no other honest coinjoiners in your group, so try again in the next round.

Suppose the trolls did rounds 1 and 2 correctly and are now in round 3. There are two ways a troll can do round 3 incorrectly: not provide valid "btc sigs" for their inputs or not provide a valid ring signature proving they were in round 1. All honest parties discard messages that lack valid ring signatures, so that part has no effect, it is as if they never sent the message. And if any troll did not send valid btc sigs, kick his inputs out of the group and restart with the remaining honest people. Continue this procedure until round 3 is done or you are the only coinjoiner left, which just means there were no other honest coinjoiners in your group, so try again in the next round.

If any troll goes through rounds 1, 2, and 3 properly, then they were not a troll, they did the coinjoin all the way through, so huzzah! But by the above methods you can kick a "real troll" out of any round (1, 2, or 3) and then redo the coinjoin with the remaining honest participants. This seems better than using fidelity bonds which make it so that many bitcoin holders cannot participate in joinmarket. Please let me know if you see any flaws in this protocol. I hasten to add, I have not implemented this "kickout protocol" yet, so Emessbee is currently flawed in exactly the way you identified: sybils can flood any attempt with fake messages to disrupt it and stop it from happening. But if Emessbee works in the happy path (it does) and if the kickout protocol can "enforce" the happy path, then I think we're in good shape.

Yes, you can find a "regular" coinjoin coordinator that's running behind tor and hope whoever is running it continues to successfully hide from the government

They can make any argument they like but good luck shutting down every nostr relay e.g. in Jamaica, Russia, and Cuba. Also, this argument would imply that every text forum is a money transmitter. Good luck getting a court to agree.

Yes, you could post the messages in a group chat on Twitter, Telegram, Signal, IRC, Session, Simplex, Tor, or literally any other place where it's possible to (1) send a message and (2) read other people's messages

You could probably even find a government website where you can do that

The only way they can stop this service is by taking down the entire internet

Here is the demo video from the BTC++ hackathon:

And in the following video (from BTC++'s Workshop Day) I outline the protocol in greater detail:

Holding for the Longest Time

It calls itself "the Ark second-layer payment protocol"

That is different from calling itself "the payment layer," as if there is no other

There is no other second layer payment protocol called Ark so it is perfectly reasonable to use a definite article ("the") in order to distinguish this layer two from other second layer payments protocols called other things (e.g. lightning)

You sound upset, why? What is wrong with more second layers? Devs are just devving my friend, it's what we do

not easy

for hedgehog to work you have to create a preimage & hash in every transaction, as well as two bitcoin signatures. A guy in this video shows how to create a preimage & hash with pen and paper. It looks like it would take about 8 hours of full time work and you'd probably make a mistake somewhere, so you'd likely need a team of three people to check your work. It is my understanding that creating a signature manually is about twice as difficult as creating a hash manually, and you need two of those per transaction so it's about four times as much work to make the signatures. So you're looking at five days of 8 hours of work for a team of four people -- per transaction.

But why do this with pen and paper? In this hypothetical scenario, did the USA also confiscate and ban all graphing calculators? It only takes a graphing calculator about a second to calculate a hash or a signature, so you'd simply have to program it for that -- and I'm sure such programs would be released as shareware. (There's one for gameboy already, so start with that and modify it for a ti-86, which should be easy because they are both 8bit processors with Assembly support. Or literally use a gameboy.)

I have had no problems leaving it closed most of the time and only opening it up when I need to make a payment. But since I live on bitcoin and use it in several of my day to day purchases, I generally open it up multiple times per day. Electrum also has a watchtower option so you can find someone who's running one and ask them if you can plug their watchtower info into your electrum wallet.

Watchtowers do not have custody of your funds but they do have some presigned transactions they can broadcast to close your channels, and you're trusting them to do that if you don't think you can get online in time to punish your counterparty if they try to cheat. There are instructions for running a watchtower here, consider running one for your friends and having them run one for you. It is my understanding that if you don't use a watchtower, you are safe as long as you open up your lightning node at least once during every two week period.

Electrum is the best

I don't know why it gets so little attention. IMO it's far more normie friendly than something like LND, CLN, or Eclair, because it's designed to be used visually with its integrated, excellent gui. The others have UIs but you have to pick one, and they are made by other devs with varying degrees of confusingness mixed in. Electrum strikes the right balance IMO: normies can use a standardized interface that looks nice and matches what they'd expect from a desktop or mobile app, and power users can access advanced features from the menus, or, if that's not enough, there are the command line and RPC options.

Try bitpac.org -- it's super easy to set up a multisig there, all you need is a nostr profile from each party

I used joinmarket to coinjoin my coins, and the best part was, I never paid a cent

I just ran it in "market maker" mode and people paid me to coinjoin with them

I also wrote a little tool here that alerts you via Telegram whenever someone pays you to coinjoin with them, and tells you how much money you made

I doubt it still works but maybe I should check and make sure

I think they would go after any node that relays your transactions and charge them with transmitting money sans KYC

Well, I don't think they would do that, but I wonder if they want node operators to worry about a dragnet operation -- "if I keep running this node they're coming after me!"

For a while I had the impression that you are only a money transmitting service if you accept currency from person A and give it to person B. But that seems to be changing. In their prosecution of Samourai, they indict Samourai as an unlicensed money transmitter for (among other things) running the Ricochet service, which is just an inbox where people send signed "raw" bitcoin transactions that Samourai broadcasts at random future times (they do this to disrupt timing analysis and to confuse chain analysis software). If merely "sending someone else's signed bitcoin transaction to the network" (!) counts as transmitting money, then every bitcoin node that relays blocks or mempool transactions also counts as a money transmitter. So if you've ever used a wallet that doesn't do KYC on you and does somehow manage to get your bitcoin transactions into bitcoin, it looks like the FBI is warning you to stop.

Chrome OS is quite capable and so far I think Google has done a great job making it normie friendly

Except for one thing: spying on users is not user friendly, it's user hostile, and Chrome OS loves to spy on its users