Bitcoin Forum
September 22, 2024, 07:40:19 PM *
News: Latest Bitcoin Core release: 27.1 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 [343] 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 ... 590 »
6841  Alternate cryptocurrencies / Altcoin Discussion / Re: compiled wallet work on unbuntu but not working moved to another ubuntu server on: April 07, 2016, 11:24:28 PM
when I try to run the ubuntu wallet, mycoin-qt
it shows: error while loading shared libraries: libdb_cxx-5.1.so: cannot open shared object file: No such file or directory

I must run command: sudo apt-get install build-essential libboost-all-dev libcurl4-openssl-dev libdb5.1-dev libdb5.1++-dev git qt-sdk libminiupnpc-dev


Is there any way I can include the libraries in the mycoin-qt file  so I do not need to inlude the libraries?
I think you need to statically link the libraries when you compile.
6842  Alternate cryptocurrencies / Altcoin Discussion / Re: compiled wallet work on unbuntu but not working moved to another ubuntu server on: April 07, 2016, 07:43:54 PM
what is the exact error that happens?
6843  Bitcoin / Bitcoin Technical Support / Re: Bitcoin lost? on: April 07, 2016, 05:01:41 PM
What is the transaction id of the transaction?
6844  Economy / Digital goods / Re: How to buy BCT Accounts on: April 07, 2016, 01:45:00 AM
I have seen some threads that sell higher rank bitcointalk accounts. What are the methods so that i can securely get one?
The account is connected within an email, what about that ? I am new to account trading. Please help.
You can open a WTB (want to buy) thread looking for an account. Usually you state your budget and the account rank you want and any specifics. Or you can look around the Digital Goods and Auctions sections and find threads where people are looking to sell accounts. You can buy an account from there, they usually specify the price and the stats of the account that is being sold. When you buy an account, you should use an escrow and always ask for a signed message from an old address posted by the account. The escrow will check the account is what was specified and that the signed message is valid. Then he will send you the account details and you should do the same. When you get an account, always change the password and email and also unset the security question.
6845  Bitcoin / Bitcoin Technical Support / Re: Error: A fatal internal error ocurred, see debug.log Core v. 0.12 WinX64 on: April 06, 2016, 02:53:12 AM
Thank you!
doing it right now.

now, what happens with the 1.9 BTC that are not anywhere, they are not in my wallet because the wallet says that it send it, and the tx is not on the blockchain Sad  can I resend the TX manually? or i just have to wait and the wallet will resend it? (if so, how long should i leave the wallet online for that to happen?

thanks!
Indkt.
It should periodically rebroadcast the transaction. However, you can just get the raw hex of the transaction and send it yourself. You can right click the transaction in the transactions list and select "Copy Raw Transaction" and then go to Help > Debug window > Console and type into the box
Code:
sendrawtransaction <pasted raw tx>
where <pasted raw tx> is just pasting what you copied there. Then hit enter and it will send.
6846  Bitcoin / Bitcoin Technical Support / Re: Error: A fatal internal error ocurred, see debug.log Core v. 0.12 WinX64 on: April 06, 2016, 02:17:30 AM
HUH so it is not a reindexing problem it is a corrupted data block then?

jeez with my ISP it would take a week to download 70 GB !, can i copy the blockchain from another core wallet?
will that work?

do I need to do a --reindex if i do that or it is not necessary?
thank you!

Yes, you can copy it from another instance of Bitcoin Core. It won't require a reindex. You will need to copy the blocks, chainstate, and database folders.
6847  Bitcoin / Bitcoin Technical Support / Re: Error: A fatal internal error ocurred, see debug.log Core v. 0.12 WinX64 on: April 06, 2016, 01:54:00 AM
It looks like you have corrupt blocks on the disk. The only way to fix this is to do a full resync, meaning you will be redownloading the entire blockchain. To do this, shutdown Bitcoin Core and go to the bitcoin data directory and delete the "blocks" folder. Then start Bitcoin Core back up and it will do a full resync, which can take several hours.
6848  Alternate cryptocurrencies / Altcoin Discussion / Re: for OSX MAC compiled wallet, whether it will run on iphone? on: April 05, 2016, 08:10:11 PM
then how can I compile a IPhone version of wallet?
You can't. You would need to completely rewrite the wallet software to be compatible with iOS.
6849  Alternate cryptocurrencies / Altcoin Discussion / Re: for OSX MAC compiled wallet, whether it will run on iphone? on: April 05, 2016, 07:57:22 PM
No. Mac OSX and iOS are two completely different operation systems.
6850  Other / Beginners & Help / Re: Blockchain question/btm on: April 05, 2016, 07:06:18 PM
Just 10 new addresses. It is not possible to know whether multiple addresses belong to the same wallet unless a transaction happens where those addresses are the inputs. If you use 10 new addresses, you should be fine.
6851  Other / Meta / Re: question on local rules on: April 05, 2016, 01:34:39 PM
You can't change the rules after the fact for the same reason why you can't self-mod a thread after you created it as it wouldn't be fair. As shorena said, just lock the thread and create a new one (and ideally self-mod it if you want to inact your own rules).
So I can't do what I did here: https://bitcointalk.org/index.php?topic=1423718.msg14425704#msg14425704?

-snip-
New local rule: franky1 is banned from this thread from this post onwards.

Nope.
Why not? It isn't retroactive.
6852  Bitcoin / Bitcoin Discussion / Re: Clearing the FUD around segwit on: April 04, 2016, 11:50:54 PM
Segwit is all too vulnerable. It is too new.
And while it maybe "tested", effects cannot be fully understood.
And that begs the question: When is it not "too new"? If it is never deployed on such a scale as Bitcoin, then it will always be new to Bitcoin and the effects of it on the network the size of Bitcoin's cannot be known until it is tried on the Bitcoin network. No altcoin is at the same level as Bitcoin, a new altcoin certainly wouldn't. The testnet is most definitely not on the same level of Bitcoin. So sure, while we could test it on the testnet and get most of the technical bugs out (as they have been doing with segnet), it is not possible to fully understand the entirety of the effects that segwit, or any major change for that matter, on the economy and non-technical aspects of Bitcoin without actually doing it. By that logic then, Bitcoin would never be able to evolve and change in the future because the effects of any change cannot be fully understood.

Fair point, but some changes are more far reaching than others.
As in the situation of segwit being so new, if there is any risk of destroying Bitcoin, that is a risk to far.

The effects of a small block size increase is maybe more generally understood than the intricacy's of segwit.
I don't feel the same risk of destroying Bitcoin applies.
That is of course personal preference. You can think whatever you want of the risks, and form your own opinions, that's fine and up to you, I'm not going to try to sway you. The main point of this thread was to stop many misconceptions and misinformation that people spread and to present the facts about segwit. The opinions you make of it are completely up to you.
6853  Bitcoin / Bitcoin Discussion / Re: Clearing the FUD around segwit on: April 04, 2016, 11:26:20 PM
Segwit is all too vulnerable. It is too new.
And while it maybe "tested", effects cannot be fully understood.
And that begs the question: When is it not "too new"? If it is never deployed on such a scale as Bitcoin, then it will always be new to Bitcoin and the effects of it on the network the size of Bitcoin's cannot be known until it is tried on the Bitcoin network. No altcoin is at the same level as Bitcoin, a new altcoin certainly wouldn't. The testnet is most definitely not on the same level of Bitcoin. So sure, while we could test it on the testnet and get most of the technical bugs out (as they have been doing with segnet), it is not possible to fully understand the entirety of the effects that segwit, or any major change for that matter, on the economy and non-technical aspects of Bitcoin without actually doing it. By that logic then, Bitcoin would never be able to evolve and change in the future because the effects of any change cannot be fully understood.
6854  Other / Meta / Re: question on local rules on: April 04, 2016, 10:22:03 PM
You can't change the rules after the fact for the same reason why you can't self-mod a thread after you created it as it wouldn't be fair. As shorena said, just lock the thread and create a new one (and ideally self-mod it if you want to inact your own rules).
So I can't do what I did here: https://bitcointalk.org/index.php?topic=1423718.msg14425704#msg14425704?
6855  Bitcoin / Bitcoin Discussion / Re: Clearing the FUD around segwit on: April 04, 2016, 10:18:54 PM
before segwit is released someone can make a segwit tx. where the witness data is not part of the transaction.
Yes, but only for spending from an output of the type OP_0 <20 bytes> or anything similar. The witness data must still be in the transaction when you are spending from an output that has anything like OP_CHECKSIG in the output script.

i think knightdb cannot get beyond the concept that segwit is not foolproof. so its best i leave him to wallow in his small box of bug free perfect code, cushioning himself with candyfloss clouds and pink unicorns. blissfully ignorant that the world is not the dream laid out on whitepapers, while he pretends it is

have a good month everyone
I think franky1 cannot get beyond the concept of how bitcoin works and is just spouting bullshit to make himself seem better than anyone else. He simply doesn't know how bitcoin works or is trolling.


New local rule: franky1 is banned from this thread from this post onwards.
6856  Bitcoin / Bitcoin Discussion / Re: Clearing the FUD around segwit on: April 04, 2016, 07:55:30 PM
Just to summ up / that attack would be like that:
A miner
1) modifies his own mining code to enter  already the SW link into the correct place
2) mines a BAD block NOW, Long time before SW goes live
3) Now he can do lots of real txs like spending BTC (but get back when)
4) SW goes live and all blocks down to his BAD block get orphaned and his spending from 3) are neglegted
? correct ?
Soft-forks are not enforced on the older parts of the chain. Only in blocks from two weeks after 95% of the hash-power had signaled their intent to enforce (counted over a 2016 block interval after the change start-time).

For prior soft-forks, like strictder, there are many historical violations before where it was enforced. It does not make the chain invalid, only violations after the point where the new rule's enforcement begins would do so.


Thanks & yes, I got that. But this soft fork happens at 4) or two weeks later.
The question is, whether the new coded miners (SW enabled) will orphane the non SW chain down two that BAD block made in 2)  because they will all agree that this BAD but old block is the last valid SW one since it contains the correct LAST  correct SW  entry?
The problem is that the bad block cannot exist in the first place. You cannot spend from an output that you do not own. Segwit does not change this behavior.
6857  Bitcoin / Armory / Re: Bitcoin Core 0.12 and Armory 0.94. Blown away. Is this true?!! on: April 04, 2016, 07:54:03 PM
Strongly advise not to attempt Bitcoin pruning mode with Armory.
Not just strongly advise, but you actually can't. Armory will not work with a pruned Bitcoin Core at all.
6858  Bitcoin / Bitcoin Discussion / Re: Clearing the FUD around segwit on: April 04, 2016, 11:42:24 AM
franky went on irc to try to explain his scenario. this is the part of the exchange that matters because this is wher ethe flaw in his attack is explained (and i have been giving this explanation for the past couple of pages). Franky is testicools here.

Quote
testicools> ok.. lets try this from a different angle. maybe that would clarify it. i make a transaction to spend satoshis 2009 stash.. BEFORE the checkpoint. if your saying anyone can spend that transaction after i have made it.. then goodluck
<CodeShark> how do you intend to spend satoshi's 2009 stash unless you have satoshi's private keys?
<testicools> because im using segwit code before its released so the signature doesnt get validated..
<CodeShark> you still need to have valid signatures to spend satoshi's stash
<CodeShark> satoshi's stash is not held in anyone-can-spend outputs
<testicools> old clients wont see the signature area..
<CodeShark> those signatures will be in the old area
<CodeShark> to spend a nonsegwit output you use a nonsegwit input
<testicools> not if i write a segwit transaction
<sipa> that would be invalid
<sipa> he output being soent determines where the signatures go
<testicools> but sgwit transactions are not invalid because old clients just treat them as funky transactions
<sipa> the outout being soent determines where the signatures go
<sipa> you can't use a segwit transaction to spend satoshi's coins. not to old clients, not to new ones
<sipa> please read up on the design
<testicools> so no one can move coins between old and new.. that makes segwit useless ..
<sipa> yes you can
<sipa> being segwit is a per-input and per-output thing
<CodeShark> to spend a nonsegwit output you use a nonsegwit input - the transaction containing this input can still have segwit outputs
<sipa> you can have a transaction that spends from a segwit output and moves to a normal one or the other way around
<sipa> but to spend a non-segwit output, you need non-segwit input
<sipa> and the other way aroundt
6859  Bitcoin / Bitcoin Technical Support / Re: Anyway to speed up a non confermed transaction on: April 04, 2016, 01:32:06 AM
I dident know anything about bitcoin was just learning on the fly so I had a blockchain walet with my coin in It and I have a coinbase account to sell what I wanna sell but I was nervous I'd send it to the wrong address n lose my 200 so I just did like a test send I dident know about dust and all that. I'm saying once it clears or goes back I'll be able to send most my coin to my coinbase account right?
Yes
6860  Economy / Service Discussion / Re: Bitcointalk Escrows - Trade Safely! on: April 03, 2016, 11:30:55 PM
please advise me how to contact them for trade here using the escrow system here? need to have an escrow to minimize the risk.are those escrows trustworthy?
Just send the escrow a PM with the details of the trade. Make sure that you check the escrow's ANN thread for exact details on what you should do and what the escrow will do. The escrows listed on the OP are considered trustworthy.
Pages: « 1 ... 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 [343] 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 ... 590 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!