Search content
Sort by
Showing 20 of 22 results by Emilstud
Hallo, habe vor einem halben Monat einen Vortrag im Stratum 0 über die Entwicklung mit der Bitcoin Core API gehalten.
Könnte vielleicht für euch ganz interessant sein.
Hier der Link:
https://www.youtube.com/watch?v=VS03lQQRYFc
Könnte vielleicht für euch ganz interessant sein.
Hier der Link:
https://www.youtube.com/watch?v=VS03lQQRYFc
However I don't think this should be a BIP as it doesn't need to be in the reference implementation,
a BIP is a "bitcoin" improvement protocol not "bitcoin core" improvement protocol. in other words they don't have to be in reference implementation (bitcoin core) to become a BIP. for example there are BIPs that aren't in it or even anywhere else for that matter. example: BIP178 which is a versioned WIF proposal which isn't used by any wallet. or BIP39 which is mnemonic code (generating a seed phrase part) is not used by bitcoin core.
This is a decent idea but there are a few caveats :
Wouldnt the receiver IP need to be online 24/7? If the server is down for some reason then I guess you need to implement some sort of fallback or it wont go through...
Man in the middle is awfully scary too, especially if you're relying on a server rsponse to send your coins. You havve to worry not only if you're the receiver but also the sender. There are a lot of attack vectors that you need to proof against, with SSL mentioned by satoshi above being just a small part of it..
People will be a lot more tempted to compromise servers. You cant fake a btc addresss or claim it unless you have the privkey, but you can definitely hack servers, the damage would be massive compared to just a single compromised address.. Same goes for clientside, you can use SSL to encrypt your requests, but what about before the request goes out? I know very little about networking and the dumbest idea I can come up with would be to just fuck with your hosts file and simply redirect all your requests from someexchange.com to mywebsite.hack..
If there is something like this in the works Im sure they're all beating the idea to death in order to avoid/minimize issues like these. Just see how cryptography has very little human factor involved and yet we still see people lose their keys. If you open up a door like this imo the benefits are minimal compared to how much more room there will be for human error.
Wouldnt the receiver IP need to be online 24/7? If the server is down for some reason then I guess you need to implement some sort of fallback or it wont go through...
Man in the middle is awfully scary too, especially if you're relying on a server rsponse to send your coins. You havve to worry not only if you're the receiver but also the sender. There are a lot of attack vectors that you need to proof against, with SSL mentioned by satoshi above being just a small part of it..
People will be a lot more tempted to compromise servers. You cant fake a btc addresss or claim it unless you have the privkey, but you can definitely hack servers, the damage would be massive compared to just a single compromised address.. Same goes for clientside, you can use SSL to encrypt your requests, but what about before the request goes out? I know very little about networking and the dumbest idea I can come up with would be to just fuck with your hosts file and simply redirect all your requests from someexchange.com to mywebsite.hack..
If there is something like this in the works Im sure they're all beating the idea to death in order to avoid/minimize issues like these. Just see how cryptography has very little human factor involved and yet we still see people lose their keys. If you open up a door like this imo the benefits are minimal compared to how much more room there will be for human error.
According to your hosts file tweak.
This would be impossible with SSL.
The SSL certificate is unqiue. It cannot be tampered unless you have the private keys.
My idea was if you send a transaction, a confirm dialog will pop-up with the public key of the fetched SSL cert. The author of the website should put his SSL pubkey onto his website so users can verify it with the popped up private key.
@darosior
The Bitcoin wallet can also sign the cert on it's own.
My idea was to use SSL certificates just for the fingerprints to avoid fakers by DNS spoofs and Man-in-the-Middle attacks.
SSL is the solution for probably all cons on the list.
@achow101
Thank you, I will take a look at it
The Bitcoin wallet can also sign the cert on it's own.
My idea was to use SSL certificates just for the fingerprints to avoid fakers by DNS spoofs and Man-in-the-Middle attacks.
SSL is the solution for probably all cons on the list.
@achow101
Thank you, I will take a look at it
⭐ Merited by vapourminer (1) ,bones261 (1) ,pooya87 (1) ,o_e_l_e_o (1) ,LoyceV (1) ,Jating (1) ,ETFbitcoin (1)
Hello Bitcoin Community,
a long time ago there was a feature called ip transactions.
It worked like this:
1. You enter the IP-address of a recipient
2. A node which used this IP created a new address and informed the sending node about this address.
It has been removed in version v0.8 due to a lack of security.
The main key parts because it was removed were that it was very insecure because of Man-in-the-Middle attacks.
I thought that it would be really cool if you could send Bitcoins to donate.example.com.
The secure way would go through SSL.
For example:
If you enter an IP-Address/Domain it would send a SSL/TLS request to the IP-Address (I will call it server by now).
The server responds with a new generated address.
During this process SSL/TLS will be used to verify authenticity.
After the user clicked send, a message box will popup with the public key of the certificate. The user then can verify if this public key truly belongs to the owner of the IP-Address (For example if the owner provides the ssl pubkey on his website) and then confirms the transaction.
Additionally this can also be implemented in the bitcoin uri scheme:
bitcoin:donate.example.com?amount=1&sslpubkey=9A:62:5E:8B:53:D9:B0:74:10:FC:D5:6B:0F:D5:9B:3B:D9:71:4A:82
please execuse me if this URL is malformed, was too lazy to do url encoding.
Then the SSL fingerprint would be verified automatically.
Would be nice for donation receivers who want a new address for every transaction I will go onto this later.
Another big advantage is that every time someone wants to send Bitcoins to an IP-Address a new Bitcoin address is being generated.
This is really nice for people who want to use a new address for every incoming transaction.
I know it is also possible with today's methods but this would be much easier.
I see lots of sites using static Bitcoin addresses for donations. This is good for transparency but not as good as a new address when it comes to privacy.
Also very nice for only shops who want to protect their customers.
What do you think about my idea?
a long time ago there was a feature called ip transactions.
It worked like this:
1. You enter the IP-address of a recipient
2. A node which used this IP created a new address and informed the sending node about this address.
It has been removed in version v0.8 due to a lack of security.
The main key parts because it was removed were that it was very insecure because of Man-in-the-Middle attacks.
I thought that it would be really cool if you could send Bitcoins to donate.example.com.
The secure way would go through SSL.
For example:
If you enter an IP-Address/Domain it would send a SSL/TLS request to the IP-Address (I will call it server by now).
The server responds with a new generated address.
During this process SSL/TLS will be used to verify authenticity.
After the user clicked send, a message box will popup with the public key of the certificate. The user then can verify if this public key truly belongs to the owner of the IP-Address (For example if the owner provides the ssl pubkey on his website) and then confirms the transaction.
Additionally this can also be implemented in the bitcoin uri scheme:
bitcoin:donate.example.com?amount=1&sslpubkey=9A:62:5E:8B:53:D9:B0:74:10:FC:D5:6B:0F:D5:9B:3B:D9:71:4A:82
please execuse me if this URL is malformed, was too lazy to do url encoding.
Then the SSL fingerprint would be verified automatically.
Would be nice for donation receivers who want a new address for every transaction I will go onto this later.
Another big advantage is that every time someone wants to send Bitcoins to an IP-Address a new Bitcoin address is being generated.
This is really nice for people who want to use a new address for every incoming transaction.
I know it is also possible with today's methods but this would be much easier.
I see lots of sites using static Bitcoin addresses for donations. This is good for transparency but not as good as a new address when it comes to privacy.
Also very nice for only shops who want to protect their customers.
What do you think about my idea?
Hi I just saw this account https://github.com/satoshinnakamoto. This account has a Dave Kleiman profile picture and was created in Feb this year. This account has also contributuons in Bitcoin Core with timestamps from 2010 how is that possible ? I heard that all of satoshis contributions are linked with non-github-bitcoin. I cannot imagine that this is Satoshis account. Maybe this account was created by his E-Mail hacker
Re: How satoshi could be anonymous when he was the only full-node ?
He could have paid a kid in India to do it for him. I think there are many ways around the full-node theory
But how he paid the kid anonymously ? Probably not with bitcoins
Re: How satoshi could be anonymous when he was the only full-node ?
I think there was more than 1 node when he launched it, if that was the case then anyone else was able to take control of the blockchain at that time.
Second thing, is the domain name bitcoin.org, how he used to purchase it ? Purhapse any anonymous payment method at that time like Liberty Reserve or ...
But at that time, why he would manage to keep him self anonymous with this revolutionary technology ? except if he didn't want that someone will make pressure on him in the futur to stop or limit it.
Second thing, is the domain name bitcoin.org, how he used to purchase it ? Purhapse any anonymous payment method at that time like Liberty Reserve or ...
But at that time, why he would manage to keep him self anonymous with this revolutionary technology ? except if he didn't want that someone will make pressure on him in the futur to stop or limit it.
He bought it at AnonymousSpeech. Probably he used somethibg like paysafecard. The only guy who had the ability to know who satoshi really is, is Mr. Weber the owner of anonymousspeech. But if he cares about the privacy of his user, he already deleted this infos
Re: How satoshi could be anonymous when he was the only full-node ?
The most known day 1 bitcoin users are now dead 
. (Hal Finney, Dave Kleiman) so we cannot ask them for their logs. Maybe another bitcoin pioneer still have logs.
. (Hal Finney, Dave Kleiman) so we cannot ask them for their logs. Maybe another bitcoin pioneer still have logs.Re: How satoshi could be anonymous when he was the only full-node ?
In the bitcoin source code is a hardcoded peer list arent it ? The hardcoded list should exist in v0.1 otherwise I couldnt imagine how the peers found each other abd the installation guide by satoshi said that you just need to extract the zip file and run BITCOIN.EXE.
How satoshi could be anonymous when he was the only full-node ?
Hi, how satoshi could be anonymous when he was the first and only node (9th of January 2009)? You cannot run a server over tor arent ? Did he rent an anonymous server ? Has anybody informations about that ?
Hi, I know the risk when I delete my wallet.dat, all my privkeys are gone if they are not backuped. But on empty wallets it's no problem to delete the wallet.dat because there aren't any funds on it.
My question is, when I delete the wallet.dat, will Bitcoin Core generate a new one for me or will there be thousands of error messages ?
Greetings Emil
My question is, when I delete the wallet.dat, will Bitcoin Core generate a new one for me or will there be thousands of error messages ?
Greetings Emil
Some tips to protect your wallet on smartphone :
1: make sure to Delete all the apps you don't use.
2: When using your wallet, make sure NO background apps running.
1: make sure to Delete all the apps you don't use.
2: When using your wallet, make sure NO background apps running.
I don't know the situation on android because I'm an IOS user but on IOS every app is sandboxed so the apps can't effect each other so I don't understand these two statements
A long time ago a person with the name Satoshi Nakamoto had a great idea...
Time-Line:
* 2007: Satoshi Nakamoto had the idea of bitcoin and started coding
* 18th August 2008: Satoshi registered the domain bitcoin.org at anonymousspeech
* 31. October 2008: Satoshi created the whitepaper about bitcoin and sneded it to a cryptographing mailing list
* 3rd January 2009: Satoshi mined the genesis block and starts the network. That was the beginning of bitcoin
* 9th January 2009: Satoshi published Bitcoin Core v0.1
*2010: Laszlo bought a pizza with bitcoins. This was the first physically purchase with bitcoins
*13th. December 2010: Satoshi left us
*April 2011: Satoshi said that he went on other things. After that statement nobody heard anything about satoshi again.
Time-Line:
* 2007: Satoshi Nakamoto had the idea of bitcoin and started coding
* 18th August 2008: Satoshi registered the domain bitcoin.org at anonymousspeech
* 31. October 2008: Satoshi created the whitepaper about bitcoin and sneded it to a cryptographing mailing list
* 3rd January 2009: Satoshi mined the genesis block and starts the network. That was the beginning of bitcoin
* 9th January 2009: Satoshi published Bitcoin Core v0.1
*2010: Laszlo bought a pizza with bitcoins. This was the first physically purchase with bitcoins
*13th. December 2010: Satoshi left us
*April 2011: Satoshi said that he went on other things. After that statement nobody heard anything about satoshi again.
Mt. Gox was the monopole BTC-Fiat Exchange.
Back in 2014 this site got hacked and the hacker stole 750k BTC.
After this accident Mt. Gox went down.
That should help:
https://en.wikipedia.org/wiki/Mt._Gox
Back in 2014 this site got hacked and the hacker stole 750k BTC.
After this accident Mt. Gox went down.
That should help:
https://en.wikipedia.org/wiki/Mt._Gox
Hi, I have a Bitcoin Full Node in my network. If I want to setup a new full node on my network I can tell my new node to download the chain from only this node. But can I tell my main full node to share only with this peer ? (It will be a tempoary thing until the second node is fully synced). Because downloads inside a Local Network are xtreme fast.
Hi, I started a full node 20 minutes ago. I forwarded port 8333 tcp and the download is very fast. After 20 minutes I was at block 135100 
I download around 300 blocks per second is this normal with a 400Mb/s Down and 40Mbs Up connection ?
I download around 300 blocks per second is this normal with a 400Mb/s Down and 40Mbs Up connection ?
Cold Wallets are the safest wallets.
Cold means that it is not connected to the internet.
Hot Wallets are always conncted to the internet like desktop wallets.
Mobile wallets are an exception because they are sandboxed and can't effected by malware
Safe Storing Methods:
* Paper Wallets (walletgenerator.net)
* Hardware Wallets (Ledger, Trezor)
* MultiSig Wallets where one private is stored on a cold wallet
Unsafe Storing Methods:
* Desktop Wallets (Bitcoin Core, Electrum, Jaxx, Exodus)
*Mobile Wallets (They are sandboxed)
* Exchanges (Coinbase, Binance)
Always remeber YOU ARE YOU OWN BANK.
You can use desktop wallets if you trust your computer. But you should know that no system is safe for malware.
For newbies I recommend Exodus.
If you want an open-source alternative than you should take a look at Electrum.
When you want to hold larger assets than use a Ledger Nano S or paper wallet instead of a desktop wallet.
Cold means that it is not connected to the internet.
Hot Wallets are always conncted to the internet like desktop wallets.
Mobile wallets are an exception because they are sandboxed and can't effected by malware
Safe Storing Methods:
* Paper Wallets (walletgenerator.net)
* Hardware Wallets (Ledger, Trezor)
* MultiSig Wallets where one private is stored on a cold wallet
Unsafe Storing Methods:
* Desktop Wallets (Bitcoin Core, Electrum, Jaxx, Exodus)
*
* Exchanges (Coinbase, Binance)
Always remeber YOU ARE YOU OWN BANK.
You can use desktop wallets if you trust your computer. But you should know that no system is safe for malware.
For newbies I recommend Exodus.
If you want an open-source alternative than you should take a look at Electrum.
When you want to hold larger assets than use a Ledger Nano S or paper wallet instead of a desktop wallet.