-snip-
I am asking "What can I do to confirm them into blocks?"
-snip-
Keep rebroadcasting the transactions, either via the known interfaces/APIs or with your own node. I didnt look deeply into each TX so I might be missing something, but besides a slighly low fee they seem to be fine. If you used a (ponzi) script to create them, consider only using confirmed inputs as chains after a certain length (25?) get refused by nodes past a certain version (0.12?). Dont know the exact number, but I think you get the idea. Not gonna work here. -snip-
It is confirmed. Go on.
Time to wait for the next in the chain -> https://blockchain.info/tx/f65d87013d8965128e0b6f304cf87480694b7622947b9c3a1c08c834befb5b45Edit: might take a while... |
|
|
|
The reason is displays the error is probably because your transaction does break the network rules. Do you have an output of under 5430 satoshis?
No it was 0.5 btc with a .126 mbtc fee. Do you use an old version? They create (now) invalid signatures. |
|
|
|
Hey, has someone seen this request??
The bitcoin address you used to sign is not tied to the account you want restored. The process to get an account restored is very simple. Send theymos a single PM that contains a link or PM ID where the address can be found. If its a link to a post the message must be unedited. If its a PM ID, it must not have been deleted by sender or receiver (one to keep it is enough). If you have such a link or PM ID, send a signed message in the required fashion[1] and your account will eventually get restored. Posting proof publicly may results in users from default trust to mark the account during the process to avoid further harm (mainly to other users). With all that being said, keep in mind that theymos might not restore an account regardless because they have more information than we. [1] https://bitcointalk.org/index.php?topic=497545.0I have already sent the PM to theymos. Waiting for his reply for the past 12 hours. Get comfortable, it often takes weeks, sometimes months. IIRC you can resend the PM weekly, but you should make sure that its as described above. |
|
|
|
Hey, has someone seen this request??
The bitcoin address you used to sign is not tied to the account you want restored. The process to get an account restored is very simple. Send theymos a single PM that contains a link or PM ID where the address can be found. If its a link to a post the message must be unedited. If its a PM ID, it must not have been deleted by sender or receiver (one to keep it is enough). If you have such a link or PM ID, send a signed message in the required fashion[1] and your account will eventually get restored. Posting proof publicly may results in users from default trust to mark the account during the process to avoid further harm (mainly to other users). With all that being said, keep in mind that theymos might not restore an account regardless because they have more information than we. [1] https://bitcointalk.org/index.php?topic=497545.0 |
|
|
|
You click on the little # symbol that reads "insert code" when you hover over it (on a PC). It will create code tags for you. Inside these code tags you paste the text from the code block in this post and replace message, address and signature with your data. -----BEGIN BITCOIN SIGNED MESSAGE-----
message
-----BEGIN SIGNATURE-----
address
signature
-----END BITCOIN SIGNED MESSAGE-----
-----BEGIN BITCOIN SIGNED MESSAGE-----
This is Conus
This is my current Bitcoin Address
-----BEGIN SIGNATURE-----
1ChGMGUJqxVSEJChCU7U7uQCjpMeoKuYAM
H5PtU9ChXlwb2Wcm/LoI8g25tUsgCWWGIcCAEXceu493WsrhTqLipBwImz6EvaIFlqaicULT1UIz6tMM0TQknRM=
-----END BITCOIN SIGNED MESSAGE-----
|
|
|
|
I installed bitcoind and it downloaded the whole blockchain and is fully synced, but is not listening for connections on port 8333, so it is not a full node. How do I make it accept inbound connections?
Its still a full node. Unless you set a proxy or use -conect its looking for inbound connections by default. Did you open the port on your firewall and forward it on your router (if needed). If you can rule out the firewall, make it explicitly list with -listen. |
|
|
|
-snip-
Deine 100€ kriegst du mit an Sicherheit grenzender Wahrscheinlichkeit los (vorausgesetzt du hast ein smartphone oder laptop dabei) und wahrscheinlich auch günstiger als 5%.
-snip-
Yop, bin wieder dabei. |
|
|
|
-snip- Lets assume 97.0000% of these are correct, thats 1843 correct and 57 not. In order to reach 97.5% (I assume thats when 98% will be shown) he would have to make 2223 total correct reports vs 57 bad. Thats 380 good reports without fail.
Accuracy is always rounded down IIRC, so it'll take even longer. People shouldn't worry about accuracy much, and certainly not single percentage points. Had that in mind as well. The report to moderator button, when activated, says,
"Use this function to inform the moderators and administrators of an abusive or wrongly posted message."
Is "abuse" reportable?
Depends on your definiton of abuse. Anything that is against forum rules. Is this report button also for off topic and zero or low value posts? (if so, why does it not say)
Yes, but sometimes the bigger picture needs to be painted. In this case a PM to a global mod or admin might be better. What sort of posts are people reporting?
The majority of my reports are threads in wrong sections. Which makes the "Im no snitch" comment hilarious. Looks like you have answers to that in your thread already. What is constructive and what is spam are tricky questions that may not always have an easy answer. |
|
|
|
Ein Legendary mit 1 Post/Activity wäre ja mal ein interessanter Anblick. Allein um die Reaktion mancher zu sehen wäre die Sache mir einiges Wert  Soweit ich weiß geht das sogar. Ich könnte jetzt alle bis auf einen Post löschen, würde entsprechend activity verlieren, aber nicht den Rang. Gilt aber wohl nur für Ränge Hero oder höher. Nein ich werds nicht testen um sicher zu gehen. |
|
|
|
Here are the top 50 reporters by total good reports. Thanks to everyone who reports! Even one good report is helpful. But massive thanks to those in this list: without you, moderation would be basically impossible. Although most people in this list have very high accuracies, in general there's no need to worry about accuracy too much. +--------------------+------+-----+-----------+----------+
| user | good | bad | unhandled | accuracy |
+--------------------+------+-----+-----------+----------+
| shorena | 9140 | 331 | 466 | 96.5051 |
| Lutpin | 4881 | 69 | 180 | 98.6061 |
| Cyrus | 4641 | 170 | 90 | 96.4664 |
| botany | 4202 | 149 | 182 | 96.5755 |
| mexxer-2 | 3778 | 79 | 69 | 97.9518 |
| EAL | 2882 | 72 | 141 | 97.5626 |
| hilariousandco | 2721 | 82 | 30 | 97.0746 |
| Quickseller | 2553 | 120 | 119 | 95.5107 |
| TheButterZone | 2393 | 229 | 92 | 91.2662 |
| Welsh | 2213 | 42 | 20 | 98.1375 |
| mprep | 1995 | 118 | 85 | 94.4155 |
| Foxpup | 1705 | 13 | 43 | 99.2433 |
| redsn0w | 1646 | 268 | 103 | 85.9979 |
| -ck | 1501 | 26 | 5 | 98.2973 |
| mitzie | 1499 | 65 | 31 | 95.8440 |
| deadley | 1384 | 79 | 13 | 94.6001 |
| subSTRATA | 1360 | 55 | 103 | 96.1131 |
| EcuaMobi | 1331 | 11 | 14 | 99.1803 |
| DannyHamilton | 1261 | 15 | 46 | 98.8245 |
| malevolent | 1253 | 36 | 14 | 97.2071 |
| --Encrypted-- | 1222 | 23 | 27 | 98.1526 |
| xandry | 1029 | 18 | 102 | 98.2808 |
| okae | 1014 | 0 | 0 | 100.0000 |
| dbshck | 988 | 13 | 7 | 98.7013 |
| railzand | 965 | 61 | 3 | 94.0546 |
| tmfp | 936 | 35 | 17 | 96.3955 |
| austin | 896 | 46 | 0 | 95.1168 |
| knightdk | 895 | 19 | 20 | 97.9212 |
| Lauda | 885 | 21 | 54 | 97.6821 |
| Vod | 846 | 17 | 16 | 98.0301 |
| Muhammed Zakir | 840 | 68 | 83 | 92.5110 |
| xhomerx10 | 712 | 6 | 20 | 99.1643 |
| xetsr | 709 | 43 | 43 | 94.2819 |
| dogie | 691 | 186 | 72 | 78.7913 |
| Mitchełł | 666 | 29 | 87 | 95.8273 |
| KWH | 654 | 70 | 44 | 90.3315 |
| unamis76 | 556 | 0 | 1 | 100.0000 |
| grue | 540 | 36 | 7 | 93.7500 |
| NLNico | 530 | 12 | 3 | 97.7860 |
| Grand_Voyageur | 521 | 32 | 60 | 94.2134 |
| OnkelPaul | 520 | 2 | 0 | 99.6169 |
| pedrog | 514 | 4 | 4 | 99.2278 |
| suchmoon | 509 | 70 | 135 | 87.9102 |
| LMGTFY | 507 | 3 | 2 | 99.4118 |
| whywefight | 496 | 40 | 38 | 92.5373 |
| jl2012 | 477 | 30 | 35 | 94.0828 |
| ocminer | 476 | 30 | 4 | 94.0711 |
| soullyG | 467 | 13 | 181 | 97.2917 |
| justusranvier | 462 | 25 | 1 | 94.8665 |
| Holliday | 445 | 10 | 5 | 97.8022 |
+--------------------+------+-----+-----------+----------+
"Unhandled" means that every moderator with jurisdiction over the post was unsure about the correct thing to do with the post and so left it for other mods to deal with, but no mod ever decided to act on it. I suppose it can be thought of as a "weak bad", though it's ignored for your accuracy percentage. Since so many people have so many reports, I changed the percentage on the reports page so that it uses proper rounding instead of ceil() and shows 1 decimal. Actually, I changed my mind. This would probably make people feel subconsciously paranoid about reporting. Thanks for the update, mexxer-2 and me wondered a while back whether Cyrus was still number one. I guess lutpin will be the one to overtake me then. Btw, was it actually ceil()? I thought it was floor(). |
|
|
|
Was wäre jetzt eine sichere gebühr um sicher zustellen das es schnell ankommt ?
Da du bitcoin core benutzt kannst du die eingebaute empfehlung benutzen, die ist in der eegel recht gut. Lediglich beachten das der client ein bisschen gelaufen ist ehe du bitcoin sendest. |
|
|
|
There was a thread which I had 2 posts in it but after 1 hour seems no where to be found, couldn't find my posts nothing at all.
Is this common in this forum? I know when a post gets deleted you receive a PM telling you about it but how come I didn't get anything at all?
If the thread was moved to trash you dont get a PM for your posts unless you started the thread. It happens regularly with spam, yes. |
|
|
|
You might wanna reset all the transactions from your wallet and resynchronize it.
How can I do that ? Start Bitcoin Core with the command line switch -zapwallettxs to remove the transaction from local storage. The blockchain will subsequently be rescanned for all txns related to your wallet, and you will be able to continue using your wallet. You only need to run it with -zapwallettxs once. I opened the terminal and did : open /Applications/bitcoin-qt.app --args zapwallettxes It did opened but nothing changed. Which version do you run? |
|
|
|
Assuming that you are using Electrum's mobile wallet and setting the fees there, the fees are in mBTC/kB. Hence, your fees are actually 0.0000004BTC/kB which is too low for nodes to relay it. Hence, it takes 0.00001BTC/kB since it was the relay fee in earlier Bitcoin Core revisions.
If you are thinking of putting 0.0004BTC/KB as the fees, put 0.4mBTC/kB.
I changed my setting from mbtc to btc, i now have been rejected from the node bc of the low miner fee but now the money is not back in my wallet. Electrum still is saying the it is processing, but when i check the blockchain it says it was rejected by the nodes. Is there anything i can do now or am i just ass out of the money? Blockchain.info can not speak for all nodes. Just because they dropped your TX does not mean the network has forgotten. -> https://www.blocktrail.com/BTC/tx/5d47e879f6ffa49723afa178804bd1693091a30d07cfa7061d9a324ee0512b17Im not familiar with the mobile wallet, is there a way to "rescan the blockchain", "repair" the wallet or something like that? If not you have to restore from seed. |
|
|
|
kannst ja einen WGET auf alle seiten absetzen und dann prüfen ob eine ADRESSE dabei ist wo coins drauf sind ;-)
Ich weiss zwar nicht was ein WGET ist aber ich hab alle Adressen gerade mal durch geklickt.. Nix gefunden  Das ist mehr als nur eine Seite, alle Adressen auf allen Seiten hast Du sicher nicht durchgeklickt, meine Bitcoin sind noch da wo sie sein sollen. na rate mal --> meinen Rat nicht befolgt und vorher ein Passwort drauf...   Tjoa, dann.... hat der Password-Manager vielleicht niedrige default Einstellungen? |
|
|
|
I think you are looking for security not entropy.
The two is the same, because i was not asking for keysizes which can be arbitrary if the underlying function only provides so much. The values might be the same, but they are not the same thing. For example creating a 4096 bit private key is useless (and probably invalid) if the ECDSA gives only 128 bit. So therefore the entropy is what matters not the keysize.
Well you cant use a 4096 bit private key with ECDSA as used by bitcoin and 4096 bit RSA keys are not useless even though they only provide a security level of 128 bit[1]. Scenario #1: You have spend coins received on the address in the past and thus the public key is stored in the blockchain. In this case the attacker would need 2128 elemantary operations to find the correct private key. Aka a security level of 128 bit. This ignores randomness and chance, e.g. the birthday paradox.
Scenario #2: You have never spend coins received on the address, ever. You also have not otherwise published your private key (e.g. due to a payment to pubkey instead of to an address). In this case the attacker has to break the RIPEMD160 hash in order to get to the SHA256 of the public key. Since there are no known attacks to improve from simple brute force its security is 160 bit. Once RIPEMD160 is done, an attacker would need to break SHA256 (256 bit security, unless used with reduced number of rounds) in order to get to the public key and from there try to find the private key. This however makes no sense as its way faster to just try private keys until you found one that results in the same address. As there are only 2160 different (version 1) addresses due to the 160 bits of RIPEMD160 there are 296 different private keys for each address. As such you have a total security level of 160 bits.
Yes I've heard this variant before. We need some more expert's confirmations on this. Also are you sure the operations are elementary, there is a lot of hashing going on, It looks like this, and there are many operations going on, not just elementary, so I think there is more security here: -pic here- True calculating a bitcoin address from a private key is not an elemantary operation. It would make an attack even slower for an unused address. I dont think it matters much though. 2 160 or 2 128 are both very large search spaces. [1] might not be the exact correct value, cant find a table atm. |
|
|
|
Dann sind 150€ somit vernichtet.
Die wallet.dat ist verschlüsselt, somit ohne das passende Passwort wertlos.
Naja... Wieviel "bit" stärke hatte das password den? In der regel sollte er einfach ein neues password nach gleichem schema erstellen können und dabei eine zahl angezeigt bekommen. Bei 40 bit kann man ggf. n monat reichenleistung draufwerfen um ans password zu kommen. Aber mal anders... haben die Backups auch ein password oder hat er deinen rat nicht befolgt? |
|
|
|
|
Show Posts
