Bitcoin Forum
June 21, 2024, 05:09:09 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 »
1  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] the Internet of Coins on: January 05, 2015, 09:43:08 PM
Very interesting project, well done for the whitepaper Smiley

I've read the whitepaper and I have a few questions:

In page 3 I was very puzzled about how the multisig configuration would work and I imagined something similar to what I found later in section 10. Maybe it's a good suggestion to add a reference to section 10 for the explanation

In the combination of multisig, how many keys are required to unlock the value sent? All the keys of the swarm plus Alice or Bob? Or is this an M-of-N configuration to prevent missing nodes?
Are all the required keys in one swarm/group sent to another swarm/group as backup before being sent to the users?

I understand one user creates an address to send and the other user constructs the private key to access the funds on that address
Which keys (public/private from who Alice/Bob) are signing on each part of the transaction? The steps in the graph confused me a little bit although I like the actual graph, kudos for it.


In page 5:
There is a mention to an image that is missing in that page. I imagine this refers to the image that appears at the top of page 4, is this correct?


Who creates the hybrid asset and why should I care about a specific asset or trust the issuer compared to another one? Is there any reputation system?
Who and how we set the exchange price of the hybrid asset among chains?
This is the part that I can't completely click in my head: if, for example, I create asset X in Counterparty for the value of 1 BTC and the same asset in NXT for the value of 1 BTC and tomorrow the price of NXT duplicates, then the value of my hybrid asset X in NXT is twice more valuable than my asset X in Counterparty. How do I sell/buy these assets to other people interested in buying the appreciated NXT?


Legal disclosure
I'm not responsible for any mental harm caused to any human or animal produced while reading any of my possibly stupid questions.
2  Alternate cryptocurrencies / Altcoin Discussion / Re: Nothing-at-Stake & Long Range Attack on Proof-of-Stake (Consensus Research) on: December 20, 2014, 10:58:26 AM
Regarding history attack, I will introduce in this topic another very interesting idea from NXT that is not yet implemented but could solve concerns with hidden history rebuilding, it's called Economic Clustering.

In Economic Clustering, basically, all transactions have to include a signed reference to an older block or transaction in the history, so if an attacker gets the keys of an account that used to have huge amounts of stake (those close to the genesis of the coin) and tries to reconstruct his/her own version of history in isolation it's impossible to rebuild it including the transactions of the rest of the economy and collect any of their fees, simply because the hashes of the new history will never match those included in the transactions previously broadcast.
If you already belong to the network and see the hidden branch being released your client can immediately spot the fake history as not including any transaction that you know about (from you or from a list of known companies/entities).

I see it as a social consensus: to fool the history you need to pro-actively involve a majority of the network signing the scam.
3  Bitcoin / Project Development / Re: [ANNOUNCE] Bitcoin Testing Project on: March 29, 2014, 12:06:09 PM
Is this project still alive?

I resurrected this post because I recently saw a discussion about bounty donations for development in reddit and some people wanted to contribute to bounties for testing. Original: http://www.reddit.com/r/Bitcoin/comments/213o03/contribute_to_the_bitcoin_core_development_each/cg9k7al


I know from experience that testing is a fundamental part of software development, so I hope this project is still alive and moved to another thread/forum/place but if you know this project is completely dead and testing is dying in Bitcoin we must resurrect it.

Testing is usually the biggest bottleneck to fix and improve a released software.


I saw these testing templates in github, are they actually being used?
https://github.com/bitcoin/QA/blob/master/TestPlanCreation.md
https://github.com/bitcoin/QA/blob/master/TestPlanExecution.md
https://github.com/bitcoin/QA/blob/master/TestPlanSkeleton.md
4  Bitcoin / Development & Technical Discussion / Re: Bitcoin 0.9.0rc2 is available for testing [Changelog] on: March 02, 2014, 02:32:00 PM
Great news, thanks to everybody that contributed Smiley

I started testing it on win64
5  Bitcoin / Hardware wallets / Re: Trezor: Bitcoin hardware wallet on: February 23, 2014, 12:25:37 PM
Installation went through well from github but https://mytrezor.com/ also times out for me so there is the end of the testing.

Actually http://mytrezor.com/ works and said "Trezor Browser Plugin is succesfully installed" (there is a typo in "succesfully"). Probably the extension HTTPS Everywhere redirected to HTTPS, but if I enter http://mytrezor.com/ the plugin loads fine.

Tested it on a w7x64 on FF and chrome
6  Local / Español (Spanish) / Re: LECTURA OBLIGATORIA: Las leyes aplicables a bitcoin en España on: January 25, 2014, 02:27:53 PM
Muchas gracias por los enlaces del primer post, información muy útil, aunque hacienda no haya confirmado ni desmentido nada (porque probablemente ni comprendan qué es Bitcoin), es mejor saber qué parte de la legislación actual es la más cercana y aplicarla como "buen ciudadano"
7  Bitcoin / Development & Technical Discussion / Re: [ANN] EasyWinBuilder - The Easy Way to Build Bitcoin on Windows on: September 08, 2013, 10:16:03 PM
For those with this problem: leveldb/db.h: No such file or directory
Download and use easywinbuilder in a folder inside a path with NO spaces


Now I have another problem showing several times:
...
D:\neoranga\bitcoin\src/db.h:156: undefined reference to `Dbt::Dbt(void*, unsigned int)'
D:\neoranga\bitcoin\src/db.h:162: undefined reference to `Dbt::Dbt(void*, unsigned int)'
collect2: ld returned 1 exit status
mingw32-make: *** [bitcoind.exe] Error 1


!!!!!! Error! Build daemon failed.



Any clue where the problem may be?
Will add this to the readme:
Quote
Often the source of trouble is difficult to identify as there are so many follow up issues. You can run the scripts from within SciTE or increase your command window buffer size (open command line, right click on the top left icon, properties, layout, windowbuffersize --> 9999, then start the batch file from command line).

I did not try it with drives other than C: so you might want to check for correct drive letters in the output.

Also: If you change paths make sure to stick to forward or backward slashes as in the original as the process depends on one or the other


I found the problem, I made the same mistake as worldspace user, so I downloaded minGW again but apparently the new execution still used some of the old compiled files. After removing everything, download again and run, it all worked fine, even from a different drive.

Thanks a lot for the help and even more for the great script Smiley
8  Bitcoin / Development & Technical Discussion / Re: [ANN] EasyWinBuilder - The Easy Way to Build Bitcoin on Windows on: September 08, 2013, 09:05:43 PM
For those with this problem: leveldb/db.h: No such file or directory
Download and use easywinbuilder in a folder inside a path with NO spaces


Now I have another problem showing several times:
...
D:\neoranga\bitcoin\src/db.h:156: undefined reference to `Dbt::Dbt(void*, unsigned int)'
D:\neoranga\bitcoin\src/db.h:162: undefined reference to `Dbt::Dbt(void*, unsigned int)'
collect2: ld returned 1 exit status
mingw32-make: *** [bitcoind.exe] Error 1


!!!!!! Error! Build daemon failed.



Any clue where the problem may be?
9  Bitcoin / Electrum / Re: Electrum server discussion thread on: September 08, 2013, 06:41:40 PM
Yeah! I've just got my server to work on a linux VM with the help from the IRC channel and now I was wondering if I can make it run on windows.
Is there anything that will prevent me from compiling and running the electrum server on a windows machine?
10  Bitcoin / Development & Technical Discussion / Re: Decentralization idea: Encourage mining network distribution among pools on: August 25, 2013, 01:30:47 PM
Implementation details
- Store on each block an ordered list with the bitcoin addresses that generated blocks in the past with the cumulative number of blocks created plus the time the miner took to find the last hash(record the hashing power).
So, new miners do not have an incentive to start mining yet somehow this decentralizes mining?
The original reward for the existing POW is still there, only the amount of the reward is decreased (half for example) and the other half goes to the selected candidates that proved the work divided in equal parts. I'll update the description to make this more explicit.
11  Economy / Web Wallets / Re: Blockchain.info security [FUNDS STOLEN] on: August 22, 2013, 10:28:42 AM
Are blockchain.info paper wallets with already signed transactions in Firefox vulnerable?
How can we check?
12  Bitcoin / Development & Technical Discussion / Re: Decentralization idea: Encourage mining network distribution among pools on: August 21, 2013, 06:17:02 PM
- Decreasing chances for small pools to create blocks and attract more mining power to grow. With no reward on mid-size pools all miners should prefer to mine on big pools with better expectations for return on investment, rather than supporting new pools.
I stopped reading here. This isn't correct. Expected return is not increased by using a larger pool. Mining is not a race, it's a random lottery.

But I understood that if a pool has more people it has more chances of winning the lottery, is this incorrect?

Yes, but the winnings are split proportionally among those extra people.

That said, with a larger pool it's less likely that your block reward will be orphaned by another block that manages to propagate to the network faster than yours. But that's not a big effect right now in terms of profitability because fees aren't very important - a rational miner will keep their blocks small to keep that orphan risk down.

That makes sense to me.

The centralization problem is that a new small mining pool or an existing pool that becomes small after the arrival of a new ASICs pool has no incentives to continue mining because the expected time to find a block could become bigger than a lifetime. Therefore, it's better join the bigger pool to receive a fraction of the reward now at current difficulty than expect a large reward in an infinite time frame, specially with increasing difficulty.
This is exactly what happens right now with solo mining.
13  Bitcoin / Development & Technical Discussion / Re: Decentralization idea: Encourage mining network distribution among pools on: August 21, 2013, 04:49:22 PM
- Decreasing chances for small pools to create blocks and attract more mining power to grow. With no reward on mid-size pools all miners should prefer to mine on big pools with better expectations for return on investment, rather than supporting new pools.
I stopped reading here. This isn't correct. Expected return is not increased by using a larger pool. Mining is not a race, it's a random lottery.

But I understood that if a pool has more people it has more chances of winning the lottery, is this incorrect?
14  Bitcoin / Development & Technical Discussion / Decentralization idea: Encourage mining network distribution among pools on: August 21, 2013, 04:38:40 PM
Looking at how the ASIC market is moving and growing I started to think about these problems:
- Centralization of hashing on big pools.
- Decreasing chances for small pools to create blocks and attract more mining power to grow. With no reward on mid-size pools all miners should prefer to mine on big pools with better expectations for return on investment, rather than supporting new pools.
- Possibility for a big ASIC producer/miner to control the network.
- Not possible to confirm blocks in a very long period of time if the main pool(s) are disconnected from the network (consider a scenario with 2-3 pools/companies having 90% of the current difficulty hash power, if they drop by an attack it will take extremely long time for the next difficulty adjustment to correct this)

My idea is to encourage distribution of rewards and therefore encourage distribution of mining power.

General description: Create a list of known miners with history in mining(finding blocks), assign to them a reasonable target hash to achieve (instead of mining the main block hash) with a small reward and make the approval of the block depend on both the usual high difficulty hash and a random subset of the trusted miners.

Implementation details
- Store on each block an ordered list with the bitcoin addresses that generated blocks in the past with the cumulative number of blocks created plus the time the miner took to find the last hash(record the hashing power).
- Use the Nonce plus Fibonacci series (for example) to select the next XX(e.g. 20) candidates with their public addresses from the ordered list included in the block.
- In addition to the usual hash to be found, half (10) of those XX(20) candidates have to find an adjusted SHA256 hash.
- The adjusted SHA256 hash uses a difficulty relative to the difficulty of the last block found by this miner (not the network difficulty!). So the required number is adjusted and different for each of the candidates.
- Half (10) of those XX(20) candidates have to sign (with their private key) the next block to be found including each of their adjusted SHA256 hashes.
- The first block that includes the originally required main SHA256 hash plus half(10) of those XX(20) adjusted SHA256 hashes, each with their corresponding signatures, is considered a valid block.
- The selected addresses that proved the last block by including their adjusted SHA256 hash receive a small part of the reward divided equally (e.g. half of current reward is divided equally among all selected candidates that proved the work and the other half of the reward goes to the miner that found the main SHA256 hash).
- When there are more than half(10) of the possible XX(20) addresses that submit a valid answer, the less powerful ones get the reward (this is the time it took to find the current adjusted hash). This reduces cheating.
- Original reward for miner that finds the main SHA256 hash still exists but the amount is decreased to fulfill the rewards of the candidates.
- The list of all candidates gets updated on each new block and arranged by amount of blocks found (even with adjusted SHA256 hashes* found).
- The list of selected candidates is published in the new block with their adjusted target SHA256 hash goal so all the network knows who is responsible for next block and which are the individual targets.

- Additionally, if the main SHA256 hash for the current block has not been found for 20 minutes and half (10) of the XX(20) candidates have already found and sign their corresponding adjusted SHA256 hashes, then the block is considered valid (as a recover mechanism in case of big mining network drop).

Definitions
*Main SHA256 hash: hash to be found using the network difficulty in order to confirm a block in the current bitcoin implementation 0.8.x.
*Adjusted SHA256 hash: hash found by one of the candidates when randomly selected and included in the final confirmed block together with the rest of the candidates and the Main SHA256 hash.

Pros
- Non massive mining pools get a change to continue profitable and grow.
- Massive mining corporations loose control of the network by requiring consensus from a small group of unrelated but famous miners, reducing the centralization risk.
- Recover mechanism in case of big drop of the mining network (if the massive pools are suddenly disconnected the rest of the mining network in current implementation can't confirm a block in up to two weeks).

Cons
- Pool owners will have to manage pool jumpers that join/leave depending on pool address appearing in the 20 selected candidates
- How to enter the list of candidates without having the maximum hashing power to generate a block

Related projects I've researched:
P2Pool - https://en.bitcoin.it/wiki/P2Pool
Decentralized mining protocol standard: getblocktemplate - https://bitcointalk.org/index.php?topic=108854.0
15  Bitcoin / Wallet software / Re: Idea: Offline portable wallet on: August 12, 2013, 07:39:24 AM
I should have gotten some sleep before posting Smiley

Sorry for resurrecting an old thread but I think this is not that stupid after all (not an elegant solution either, I admit).

As far as I understand, an implementation of niko's solution would be to maintain a list of 50 addresses of 0.01 BTC in each one of them (generated at home), and give the required number
of them in the form of QR codes to the seller (who typically is a brick-and-mortar with internet connection) . Assuming that

1. there are no problems with network fees

and

2. rounding error of <1$ is acceptable to either the seller and the buyer

this would work nicely Smiley


Let's make some numbers on this solution as an example:
1- Let's say I want to move on the street with my wallet fill with 100$ in bitcoin (whatever is the exchange rate that day) for my day to day usage.
2- This translated to bitcoins will mean I'll need to have enough addresses with me to create transactions that can go as high as 100$ and as low as 10 cents (we don't want to give away too much change on every transaction)
3- The total amount of addresses will be 1000

This is possible but I imagine the fees that go into creating the daily wallet (or every time you have to get another 100$ for the bitcoin ATM) will not be trivial. In addition, the size of each transaction combining several addresses into one payment means there will be a lot of QR codes sent and waiting a long time for the camera to recognize all of them (up to 1000 addresses in one transaction to pay something of 100$).
16  Other / Beginners & Help / Re: Terminology on: August 07, 2013, 04:35:52 PM
I'm reading some posts with mentions to SPV and other types of clients and I keep forgetting what the initials mean so doing a little bit of research this is what I found.

SPV client - Simplified Payment Verification Client: A lightweight Bitcoin client that downloads only part of the blockchain
https://en.bitcoin.it/wiki/Scalability#Simplified_payment_verification

I didn't find them in the initial post so you may want to include them
17  Bitcoin / Wallet software / Re: Idea: Offline portable wallet on: July 31, 2013, 09:26:10 PM
First I'll explain the problem and then my proposed solution:
The problem is that if you want to go on holidays or somewhere where you don't have data connection in your cellphone (ey! I'm on holidays in Berlin http://tinyurl.com/bwg33vf and I want to use my bitcoins), it's not possible to pay in any shop where they accept Bitcoins because you can't broadcast the transaction from your cellphone.

Of course, you can access WiFi or pay the data-roaming cost but I imagine a much easier scenario for the end user by using the shop's Point of Sell to broadcast the transaction. Here is the explanation:
1. When paying, the user scans the QR code of the shop address where the payment has to be sent to
2. The user includes the amount to pay and signs the transaction in the phone (android/iphone/etc) wallet
3. Now the transaction gets converted into a transaction QR code in the user's phone -> Offline broadcasting
4. The shop seller can now scan the transaction QR code in the shop's POS which has to be connected to internet
5. The shop's POS broadcast the client's transaction and immediately verifies the payment


Remarks:
- Size of transaction: QR codes can't handle too much data (less than 3Kb according to http://www.qrcode.com/en/faq.html) but if the user were to use a specific address only for this offline portable wallet, like the physical wallet you take with you, the transaction size should be quite small as there is only one address to take the funds from and one to send funds to (usually).
- Security: The portable wallet should have it's own address and private key separated from the rest of the wallets, therefore, if the phone gets compromised/stolen, only one address with the day to day cash amount is lost.


This is very similar to what Armory is currently doing for offline wallets but the transference method through usb stick is not as simple as the QR code, specially in the mobile environment. I haven't seen this already implemented in any of the wallets but maybe I'm mistaken and some android wallet is already able to do this transference of offline transactions.


Let me know what you think of the idea and if there is any extra trouble you can think of.

With Mycelium, I can move funds to one my addresses, then export its private key as an on-screen QR code. The merchant, assuming they are prepared for this, scans the code and spends it away into their system.

Other private keys are not exposed. Any problems with this solution?
How do you transfer the exact amount you have to pay to the merchant to one of your addresses if you don't have network connection in the shop?
Giving a merchant the private key of an address with a random amount of bitcoins is basically like opening your wallet to the merchant and asking him/her to take the money from your wallet while you look away...
18  Bitcoin / Wallet software / Re: Idea: Offline portable wallet on: July 17, 2013, 10:09:04 PM
I have nothing against using multiple QR codes, maybe in addition to animation you can even pack several QR codes in one single screen scan, today phone cameras have enough resolution for it and a tablet screen is big enough for 4 QR codes.
19  Bitcoin / Hardware wallets / Re: [PREORDER] Trezor: Bitcoin hardware wallet on: July 16, 2013, 07:29:15 AM
hmm...
a great device.

Even better would be the standalone;

same thing with a display that can show QRcodes, a camera and a micro usb port switchable to charge only (no data) mode.

Question folks - which Android app can do offline transactions using QRcodes and a camera?

If by offline transactions with QR codes you meant this below, it has not been implemented yet, neither with QR codes neither with NFC.
https://bitcointalk.org/index.php?topic=230010.msg2424481
20  Bitcoin / Electrum / Re: Can't open Electrum on Windows 7 on: July 14, 2013, 03:07:18 PM
I'm experiencing the same problem in Win7 with 1.8, I haven't open the client for a few weeks but now it doesn't open with my "wallet.dat" file as argument, if I don't use my wallet.dat then the client opens normally asking to create a new wallet.
I couldn't figure out any trace of the error, the application simply appears and disappears in the win task manager.

Luckily I had a copy of the previous version and that one opens without any problem my existing wallet.

Move your electrum.dat file and restore from seed on the 1.8 client when prompt

Indeed, the seed restoration worked in the latest version ( 1.8 ) but of course I've lost all the customizations/notes of the original wallet Sad

We probably need to make more regression tests between versions so upgrades don't break existing client data.

Thanks for the help.
Pages: [1] 2 3 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!