Bitcoin Forum
May 03, 2024, 04:06:43 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 [61] 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 ... 158 »
1201  Bitcoin / Development & Technical Discussion / Re: Proposal: Lock my address on: May 05, 2014, 05:03:38 PM
Such kind of scheme has been repeatedly proposed. This does not improve security at all.
If you could direct us to those proposals, we may become more helpful and less repetitive.  Do you have any links?

I don't keep these links as these discussions are usually not very fruitful.

If you could keep the private key of 1UnlockingAddr safe (and you are not confident in the security of 1AddrToLock), why don't you just simply send your bitcoin to 1UnlockingAddr directly?
You must have missed this part:
Several hardcopies of the bitcoin address QR Code are displayed to collect payments from customers at retail locations.  Replacing all of them with a new address will take some time.
It is a really bad idea to use a fixed address at retail locations because you can't distinguish payments from different clients. Let say in a bar with a high turnover, many clients are paying as they are drinking, at the same time. With a fixed address it is impossible to determine whether a client has paid or not.

Having a fixed address is also extremely bad for financial privacy. Now everyone knows the turnover of your bar.

Reusing an address may also compromise security. https://bitcoin.org/en/alert/2013-08-11-android

So the answer is no. There is no way in hell we are going to make bitcoin more complex to facilitate bad practice.

If you want to require the private keys of both 1AddrToLock and 1UnlockingAddr to spend the bitcoin, why don't you simply use 2-of-2 multisignature?
That's a great idea!  It's extra work for those who want to accept bitcoin, and I assume that the vast majority of people already accepting bitcoin payments haven't done it.  Making bitcoin more secure for them seems like something that might help adoption, no?

This function is available for at least 2 years (search P2SH). It's just not very commonly used but I believe it will become much more common in 2 years.
1202  Bitcoin / Armory / Re: Armory - Discussion Thread on: May 05, 2014, 02:34:57 PM
One day we will be able to lock an exchange to a public key and they can make addresses guaranteed for us

I like that idea very much.

Could that be done without forcing the masses to learn PGP?

EDIT: or at least exchanges could make it an option for those who do wish to use PGP.

Actually no pgp, just a public seed

Theoretically a malware could replace your public seed with the hacker's. The only bullet-proof way is to register an account with an offline pgp key (or with a bitcoin key), and sign any payment requests with the key.
1203  Bitcoin / Armory / Re: Armory - Discussion Thread on: May 05, 2014, 02:31:23 PM
Regarding the virus, how would one double check that I was not victim to this attack.  **nervous**

Generate the new addresses on your cold system first, and then verify that the addresses you generate on the hot watch-only system match the addresses in the cold system.

If a computer is infected, it is completely hopeless

Let say you generated an address with the cold system, which is "1User". You send a withdrawal request to the exchange, asking them to send bitcoin to 1User. A sophisticated malware could secretly replace the address with "1Hacker" before sending the request the exchange.

Extremely valid point.

Some users on Reddit have actually been having this problem caused by extensions on google chrome. Though it could be any sort of malware, google chrome extensions just seem to be the thing lately.

Always a good idea to send a small test transaction out of an exchange before sending the whole amount.
I should be able to avoid that by noticing that I'm signing the txn to 1User on the offline rig.

No, it's not about signing, it's about sending a payment request
1204  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: May 05, 2014, 02:21:54 PM
What happened to Loaded?
I think he is still trying to get his hands around MagicalTux neck.  Wink  Grin

I think he's fine as long as his 40000 BTC is not moved: https://blockchain.info/address/14j6jLececs66ZQ8ew6vTFNiEn2NupacWJ
1205  Local / 中文 (Chinese) / Re: 本站中文版从即日起不再允许发表赌博类网站的中文广告 on: May 05, 2014, 07:06:29 AM
那個X倍網經常用大小號發軟文, 可以清理一下嗎?
1206  Bitcoin / Development & Technical Discussion / Re: Proposal: Lock my address on: May 05, 2014, 07:00:19 AM
Such kind of scheme has been repeatedly proposed. This does not improve security at all.

If you could keep the private key of 1UnlockingAddr safe (and you are not confident in the security of 1AddrToLock), why don't you just simply send your bitcoin to 1UnlockingAddr directly?

If you want to require the private keys of both 1AddrToLock and 1UnlockingAddr to spend the bitcoin, why don't you simply use 2-of-2 multisignature?
1207  Local / 中文 (Chinese) / Re: 雪球交易所p2p支付交易5月1日已经上线 欢迎大家提出宝贵意见 on: May 04, 2014, 12:15:44 PM
如果沒人違規,你們賺什麼?
1208  Bitcoin / Development & Technical Discussion / Re: Question about script on: May 04, 2014, 05:30:16 AM
I was wondering if  a bitcoin script can be written to execute based on an address total balance. For example, if total balance exceeds a number of bitcoins forward it to another address. Any thoughts?

There is nothing called "balance" in the bitcoin protocol.
1209  Bitcoin / Armory / Re: Armory - Discussion Thread on: May 04, 2014, 03:39:53 AM
Regarding the virus, how would one double check that I was not victim to this attack.  **nervous**

Generate the new addresses on your cold system first, and then verify that the addresses you generate on the hot watch-only system match the addresses in the cold system.

If a computer is infected, it is completely hopeless

Let say you generated an address with the cold system, which is "1User". You send a withdrawal request to the exchange, asking them to send bitcoin to 1User. A sophisticated malware could secretly replace the address with "1Hacker" before sending the request the exchange.
1210  Bitcoin / Armory / Re: Armory - Discussion Thread on: May 03, 2014, 06:05:22 PM
This also means new best practice is sending to offline wallet using an address created on there. Previously I got an address from the watch only copy.

Can you explain this a little further? AFAIK, the addresses generated on the offline wallet and the watch only copy are the same? Wouldn't be of much use otherwise...

A virus can compromise your watch only copy to generate addresses that aren't yours. This completely bypasses all security.

You could generate it then glance at the cold storage copy to make sure it's in the list. You may have to generate extra ones to get the number of addresses the same.

Is that a malware, or a bug in Armory?

Malware, armory is solid.

So there is not much the Armory team could do. Actually this doesn't only affect Armory. For example, a malware could replace Bitpay's address on the invoice. Even payment protocol won't help as the malware could bypass the signature check.

The lesson is no bitcoin address shown on an online computer is reliable. We need some simple solutions to verify bitcoin addresses and payment requests. Dedicated hardware wallet is the way to go.
1211  Bitcoin / Armory / Re: Armory - Discussion Thread on: May 03, 2014, 01:38:44 PM
This also means new best practice is sending to offline wallet using an address created on there. Previously I got an address from the watch only copy.

Can you explain this a little further? AFAIK, the addresses generated on the offline wallet and the watch only copy are the same? Wouldn't be of much use otherwise...

A virus can compromise your watch only copy to generate addresses that aren't yours. This completely bypasses all security.

You could generate it then glance at the cold storage copy to make sure it's in the list. You may have to generate extra ones to get the number of addresses the same.

Is that a malware, or a bug in Armory?
1212  Economy / Speculation / Re: 4th LARGEST chinese bitcoin exchange, FXBTC Chinese announces CLOSURE by May 10 on: May 03, 2014, 02:00:17 AM
I don't understand the Chinese system.

PBOC is not a lawmaker and not a court.

Is there no legal system in China? Why don't these banks and exchanges just continue to operate until they receive a court order, which they can then challenge?  Huh

Nulla poena sine lege, not in China or what?  Angry

In China, onlY the communist party matters. Lawmakers, media, PBOC and courts are all sock puppet of the communist party
1213  Bitcoin / Development & Technical Discussion / Re: Protecting Hierarchical Deterministic Structures With Multiple Scrambled Levels on: May 02, 2014, 10:57:09 AM
Why could a hacker get access to the extended private key? If you can't keep the extended private key safe, how could you keep your index sequence safe? If you, with whatever method, can keep your index sequence very safe, why don't you simply do the same for your private key?

You mentioned using multiple servers. If you think multiple server could improve the security, why don't just use multisignature transactions, with each server having different keys?

Conclusion is still the same: it provides no extra security

(Side note: is your index sequence deterministic? If not, your wallet is not deterministic)
1214  Local / 媒体 / Re: DarkMarket:丝绸之路的去中心化版本 on: May 02, 2014, 09:39:56 AM
技術是中性的, 像槍械一樣, 可以救人, 可以犯罪

有了這個就可以有去中心化的拍賣所, 人們不用受制於ebay/淘寶的規則, 也可以自選仲裁者而不需被逼付ebay/淘寶指定的服務費, 賣的東西仍然可以是完全合法的.

而且任何實物的交易都無可避免要經過郵政系統, 防止運毒是警犬的工作
1215  Bitcoin / Development & Technical Discussion / Re: Protecting Hierarchical Deterministic Structures With Multiple Scrambled Levels on: May 02, 2014, 07:47:23 AM
So how would you store the sequence: {617492810, 741109822, 1840569824, 1056489135}?

If you consider this sequence as a secret, then it is essentially part of the root private key. If you could protect this sequence, you could protect your private key with the same level of security.

If you consider this sequence as public information, then it is essentially part of the root public key and you should assume it is known by everyone

Conclusion: your proposal brings no extra security.
1216  Economy / Speculation / Re: Bitcoin long-term exponential trend (updated regularly) on: May 02, 2014, 03:11:11 AM
This bear market is worse than the 2013 one

1217  Economy / Speculation / Re: Bitcoin long-term exponential trend (updated regularly) on: May 02, 2014, 03:08:27 AM
Date:    1-May-2014
VWAP:    458.55
x:    1384
a:    0.00603
b:    -1.81597
Rsq:    0.88827
The day's expected price:    681.62
Predicted date for today's price:    24-Feb-2014
Days ahead:    -65.78
Daily price rank:    148
Predicted date for ATH ($1126):    28-Jul-2014
   
(See OP for explanation)   
   
   
   
https://www.wolframalpha.com/input/?i=e+%5E+%28+0.00602633100156526++%28+number+of+days+since+jul+17%2C+2010+%2Fdays+%29+-1.81596922051291+%29   
1218  Economy / Speculation / Re: SecondMarket Bitcoin Investment Trust Observer on: May 02, 2014, 02:39:25 AM
1256XBT bought yesterday

April 2014 data revised with latest actual holding value
1219  Local / 中文 (Chinese) / Re: 请问版主为什么我的Post总数一直在缓慢减少? on: May 01, 2014, 02:39:47 PM
好像看不到有什么贴和回帖被删了啊
或者版主删帖时通知一下

应该是有一些涉及政治的敏感内容被删除造成的。

你以為這是什麼地方?
1220  Local / 中文 (Chinese) / Re: 开放or封闭? on: May 01, 2014, 01:15:36 PM
一边是游戏机开放、上海自贸区建立,一边又是下架美剧加严网络审核,封杀比特币。
高人来指点下,zf到底想干什么?整体趋势到底是开放还是闭关? Undecided

不影響/有助獨裁統治的開放

影響獨裁統治的封閉
Pages: « 1 ... 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 [61] 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 ... 158 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!