I will make a starting bid if u accept it from 0.1 btc, i know it isnt ur asking price, but yeah, better than Nothing right?
Regards,
Joust
This isn't an auction. |
|
|
|
|
You can copy the entire directory and remove the wallet as well as using the disablewallet flag and still have the node work properly. The wallet does not contain any blockchain information
|
|
|
|
What a prick! he is acting like he owns the project.
He does... Hearn is the maintainer of the BitcoinXT fork. He is also working with Gavin to make the XT fork happen. |
|
|
|
|
you could. It is really simple. Your stupidity would probably not do anything provided that you don't do anything to mess with the node. Just download, install, and run Bitcoin Core and tada, full node.
|
|
|
|
|
There is a difference between supporting increasing the maximum block size and supporting XT. They are NOT THE SAME. Please check again and see if you can find anything about these companies that explicitly state they support BitcoinXT, not just support an increase of the maximum blocksize. Implicit statements such as supporting the max block size may not hold up in court.
Of course, I don't think this will actually work, but good luck.
|
|
|
|
I uploaded all changes on github -namecoinj. Is there a way to get the android build up to date on my s3 mini without rooting?
Install the apk. How have you been testing it? I just run it on my phone but the wallet stops syncing somewhere. At first it crashes at block 10k then it loads some more until it stops completely at some block (11964). Always producing ouOfMemoryError s. I will test installing the apk tomorrow see you then... It is possible that your phone simply doesn't have enough RAM and thus can't run the app. |
|
|
|
|
Do you have any specific requirements for the accounts?
|
|
|
|
I uploaded all changes on github -namecoinj. Is there a way to get the android build up to date on my s3 mini without rooting?
Install the apk. How have you been testing it? |
|
|
|
Awesome, thanks. I'll try building on my own machine again soon. Are you building against API level 14, as per the pom.xml?
I just used the version on his site with a logcat app and I did not see any errors. The github for the app has not been updated for a few days. Doesn't the pom.xml need to be changed to use wlcj and not namecoinj? He also already committed the changes to wlcj so I won't submit a PR. |
|
|
|
My phone made it past 10k, and is around 17k and syncing right now. I'll continue testing with adb.
Edit: I've fetched up to the second to last block. Was this version built before my last change?
you should just commit the changes to github and submit him a pull request to make sure that the changes are correct. I will also test the app on my phone. Edit: just ran the app and there were no errors. My working copy is a mess due to debugging code. I'd need to redo many of the changes cleanly to make a PR. When I get to my computer I can make all the changes she submit the PR. My code is relatively clean and I can do it quickly. Awesome, thanks! Just to confirm, with an up to date android build, you can sync to the last (not second to last) block? In that case, should we begin testing with real coins and various transaction patterns? It loads all the way. |
|
|
|
My phone made it past 10k, and is around 17k and syncing right now. I'll continue testing with adb.
Edit: I've fetched up to the second to last block. Was this version built before my last change?
you should just commit the changes to github and submit him a pull request to make sure that the changes are correct. I will also test the app on my phone. Edit: just ran the app and there were no errors. My working copy is a mess due to debugging code. I'd need to redo many of the changes cleanly to make a PR. When I get to my computer I can make all the changes she submit the PR. My code is relatively clean and I can do it quickly. |
|
|
|
My phone made it past 10k, and is around 17k and syncing right now. I'll continue testing with adb.
Edit: I've fetched up to the second to last block. Was this version built before my last change?
you should just commit the changes to github and submit him a pull request to make sure that the changes are correct. I will also test the app on my phone. Edit: just ran the app and there were no errors. |
|
|
|
|
You need to set the data directory to be the folder that contains the blocks folder.
|
|
|
|
You didn't mention any thing about post quality? If all are single line comments then no use of this senior account because you can't join any high paying signature campaign
I think the past quality is okay, although I am not a good judge if post quality. It had been a part of signature campaigns before so the post quality isn't too bad. |
|
|
|
|
I have a Senior Member that I would like to sell
Posts: 300+
Activity: 300+
Potential Activity: 350+
Registered: 2013
Feedback: neutral
I am asking for 0.23 btc for this account. The private key for an address will be added for an additional 0.01 btc should the buyer want it.
Escrow is required. I will provide the signed message to the escrow.
|
|
|
|
I must be missing something, but I thought the fork depended on blocks
mined, not on number of nodes.
So maybe the anti-XT party could spend some electricity to
mine "fake" XT blocks in order to produce illusion of 75% goal
reached. But would that really accomplish anything? Undecided miners might
still jump on the bandwagon.
Well that will not cause premature >1mb blocks, as they are scheduled no earlier than 11 Jan 2016. However it could cause the fork to occur on 11 jan 2016 without consensus. If for example 50% of the miners were XT, 25% NotBitcoinXT and the rest Core, then the fork could happen and spawn two chains with equal hash power. This could be detrimental to Bitcoin has we have previously established that such a fork is not a good thing. |
|
|
|
Let's not argue.
I am looking at some random blocks. What I see is that a single transactions is a
hash -> Don't know how to compress
Impossible without losing data. index -> why not sort by time, input etc, something 'drawn' from the data?
What index and what sorting are you taking about? We have inputs and outputs. For example, frequently we have inputs from the same origin, why not add them up for storage?
What do you mean add them up? New transactions need to be able to reference the inputs so simply "adding them up" won't allow clients to create transactions. Just looking at a set of blocks make we wonder why we can't map them in a way that we just cut of all the leading zeros. ++
That could be possible but how much space will that really save? |
|
|
|
https://github.com/bitcoin/bips/blob/master/bip-0101.mediawiki"Activation is achieved when 750 of 1,000 consecutive blocks in the best chain have a version number with bits 1,2,3 and 14 set (0x20000007 in hex)." So, what will happen if NO XT miners start setting those bits only to activate prematurely XT? Without the needed hashpower, XT will become surely an altcoin with near-zero value? Which is the goal of this or to cause confusion that forces an abort. But then what happens if a lot of xt miners are also producing blocks to the point that the forked chain had enough halshpower to survive? |
|
|
|
You need to add the flag -datadir=<path to directory> to every bitcoin-cli command |
|
|
|
|
Show Posts
