When you set up a multisig wallet, you will need enough co-signers to sign your transactions. If you set up a 3/5 co-signer multisig, you will need 3 of 5 co-signers to sign your transactions.

Any of those 5 co-signers can sign it, no need to have any co-signer in order. When a transaction gets enough co-signers sign it, it will be executed.

Before your transfer to your friend all your three channels had only send capacity, but no receive capacity. Thus your channel partners could not send you any sats or route sats through your channels, because at that moment you can't receive any sats yet.

After your payment to your friend your channel C has roughly 27,400sat receive capacity, thus that much can be routed by your channel partner of channel C through your node as long as there's a route through your channels A or B to the destination of the routed payment.

Someone else can also pay you via LN with at most 27,400sat if there's a route to your node via solely your channel partner C.

Balancing your channels, which are pretty small btw, would open up the possibility to route payments. Equal balancing means, giving each channel roughly the same local and remote capacity. What kind of balancing is preferable depends on if and how payments will flow through your Lightning node.

Don't expect too much of routing fees, three channels isn't much and your channels are pretty much too small. Some nodes would even refuse to open a channel that small with you, even if you're the one who opens the channel to them. A more suitable channel size is likely something of 2M with 1M minimum. If I were to open a new channel, it'll be 2M minimum.

You will have a hard time to earn back the channel opening fees by routing fees. I don't want to cut your dreams of routing payments but I speak of some experience with my own Lightning node. And rebalancing does cost you fees, too. You would be very lucky if you can manage the balance of your channels by tweaking routing fees of your channels only.

This could be written in one class in one file.

I rarely used Java.

Need some C/C++/C# solution.

I am looking for C# or C/C++ code to convert Bitcoin brainwallet to public address.

Has anyone written as such?
Can you share the code?

Where eventually to look for libraries to write such a code?

Thank you

...

Payments get routed through other nodes on the channels that they have open. In order for you to have paid your friend, they need to have a channel open with someone else, who has a channel open with another node, etc. until you get to someone that has a channel open with you. Payments work through forwarding - you paid node C, who used funds that they have in a channel with someone else, to pay another node, and so on, until your friend gets paid. Each node on this route can take a fee for routing your payment, so the amount that leaves your wallet will generally be a bit more than the amount that your friend receives.

There could be a number of different reasons. It could be that node C is the only one that has a route between you and your friend. It could be that the route through node C was the shortest or cheapest and chosen over other routes. In general, the channel used for payments depends on the route chosen for the payment to take.

Something useful to note here is that prior to you sending the funds to your friend, Node C could not route any transfers through you.  If Node C wanted to send to Node A (or B) and you were the ONLY path between them, then they wouldn't be able to send. This is because they didn't have any Cap on their side of the channel to send to you (for you to forward in your channel with A or B).

Now that you have sent to your friend, there are 27,410 available on Node C's side of that channel.  They would now be able to route that much to Node A (or Node B) through your node, transferring up to that amount back into your side of the channel that you have with C, while you transfer the same amount to whichever of the two nodes (A or B) that they are wanting to route to.

Google is easily the worst offender, but Microsoft isn't exactly far behind. Part of the problem is that most people interact with Microsoft via their OS, which can therefore monitor everything that happens on that device. Here's a post I made a few years ago about Windows 10: https://bitcointalk.org/index.php?topic=5190776.msg52685703#msg52685703

By all accounts, Windows 11 is even worse, and I'm sure future OSs from Microsoft will be no different.

Thankfully, it is very easy to avoid Microsoft. Just pick a Linux distro of your choice and you are pretty much done. Since you should already be using privacy respecting browsers, search engines, etc., as I mentioned above to avoid Google, then you will also be avoiding Microsoft.

At the very least there should be options somewhere in your Google account to turn off this kind of locations history. Personally I don't think it makes any difference. Google probably still collect that data, they'll just no longer show it to you in your account history.

I won't lie and say it easy to avoid all privacy invading companies and services, but it is certainly possible. For everything Google offers, there is a privacy respecting alternative. For Google Search - DDG, Startpage, SearXNG. For Chrome - Tor or Firefox. For Gmail - ProtonMail. And so on. Here are a couple of great resources to get you start on looking for alternatives:

https://prism-break.org/en/
https://www.privacyguides.org/en/tools/

Even if you don't go for maximum privacy like some of us, anything you can do limit your data being harvested is a good move.

All this could be handled as risk , you can remove wifi  for example , biut all these risk not compared from hardware walked , they can at any moment take my private key 🤣

I hope this message finds you well. I am currently embarking on a project to build my own hardware wallet, similar to popular devices like the Ledger.

Firstly, I'd like to know what components are necessary to build a functional hardware wallet. Apart from the obvious need for a secure microcontroller, I assume there are other essential parts like a display, buttons for user input, and a secure element for key storage. Could you please help me compile a list of the necessary components and their specifications? Additionally, if there are any specific brands or models that you recommend, I would greatly appreciate your insights.

Furthermore, I'm curious if there is any readily available source code or open-source projects that I can refer to while building my hardware wallet. It would be immensely helpful to have a solid foundation or reference implementation to ensure the security and functionality of my device. If you know of any existing projects, particularly ones resembling the Ledger's architecture, I would be grateful if you could share the relevant information.

I understand that building a hardware wallet involves complex considerations, particularly regarding security and firmware development. Therefore, any advice, best practices, or resources you can offer would be highly valuable to me. If you have any personal experiences with similar projects or if you know of any other forums or communities dedicated to hardware wallet development, please feel free to mention them as well.

Thank you very much for your time and assistance. I'm excited to dive into this project and look forward to your insights and suggestions.

Can you explain this? Even when running Linux without GUI, you have 6 terminals by default (CTRL-ALT-F1-6). Or just CTRL-Z or CTRL-C your sync.

I'm saying this based on generic Linux usage, I've never touched a "MyNode".

Last time i tried myNode on Virtual Machine i can access OS desktop and terminal easily. Anyway, myNode also provide guide to access terminal anytime you want. Check https://mynodebtc.github.io/advanced/linux-terminal.html.

I do this:
Then:
This can take a few seconds to complete.

No! That's not graceful at all.

I briefly read myDocs guide and found out there's script to stop Bitcoin and other services[1]. I don't know if the guide is up to date though.


[1] https://mynodebtc.github.io/bitcoin/data-from-other-node.html

There's also a "stop" rpc command that you can use with bitcoin-cli to stop bitcoind.
Use it like any other RPC commands, e.g.: bitcoin-cli stop

Just make sure that you'll call it with bitcoin-cli since it wont work with bitcoind like in the very old versions.

It's the same as "normally" turning it off. On my server, I just kill bitcoind, it closes gracefully that way.

As I am taking steps to increasing my bitcoin knowledge, securing my coin and being privacy oriented, I thank everyone who is helping me to making progress.
I have a question!
Can a well set up electrum wallet on an air gapped device be considered to be as secured as a hardware wallet?

Still working on this.
But, it does show to me at lest that we as a group should probably have better instructions for people then just download core and let it sync the blockchain.

1) Windows update forced a reboot with the patches last week and I did not notice for a few days so that added some time to the IBD. That's on me.
2) Lost power and the PC did not power on. Yes, that's on me again.

But with those 2 points above, someone who DOES know better can still drag what should be a 1 week or less IBD into a 2 week fiasco. Can you picture a normal user dealing with this.

Yes, we all know SSD, faster PC, and so on and this becomes a non issue. But someone just reusing an old PC is going to be miserable.

-Dave

Passphrases are not stored anywhere, you need to remember it.

from developer.bitcoin.org


Also, since I asked about it a while ago, there will be some variance between the mempool of different nodes:
https://bitcointalk.org/index.php?topic=5200716

With the filled mempool we are having now, depending on your config there could be a lot of difference depending on what nodes or explorers you are looking at.

-Dave

A transaction cannot be reversed once it has been confirmed, but an unconfirmed transaction can be rejected or purged out of the mempool if the sender used a TX fee that is too low in that period. Though OP's transaction is confirmed already because the TX id provided proves it, except OP provided a wrong TX id, or sent his BTC to the wrong address.

Although the majority of nodes run with the default setting of 300 MB, there is no requirement for any node to stick to this, and nodes are free to change the memory they dedicate to their mempool.

For the transactions in your mempool, yes. But as we've seen, there are other nodes such as mempool.space which have much larger mempools. As the transaction in your mempool start to get added to blocks and your memory usage drops, your node will start to accept and store these transactions from other nodes with larger mempools.