yeah I checked manually this time and I'm still watching them (the unwatch button is there). btw it did go away when I cleared my watchlist and "Show new replies to your posts" (see the third post of this thread) but that's only fixed it temporarily.
screenshots before I checked the threads manually (now they're empty): "Show new replies to your posts" pageWatchlistnotice the difference between these and what I posted above. Im not sure I get you. The watchlist only shows threads that have unread posts. Im pretty sure you have read the "missing" 3 days old threads. |
|
|
|
Hm. I actually noticed some users with gif avatars so I do believe they're accepted.
Animated gifs used to be allowed in the past. They are no longer. Those that have an animated gif as avatar now, have had it for a very long time. |
|
|
|
I mean, a one click button on the forum, like show new replies, show unread posts, show watchlist  |
|
|
|
Imagine that your nodes get DDOS at home so people move to free and cheap cloud based services to keep them up.
How does that solve the problem of having massive amounts of nodes run by a few entities on central cloud service? I would hope that we wouldn't need to depend on mass centralization to prevent DDOS attacks on the network. That wouldn't be very robust. Imagine that your nodes get DDOS at home so people move to free and cheap cloud based services to keep them up.
Imagine how actual server operators easily mitigated the DDoS attacks[1] as they are primitive and flawed. It also makes no sense that every classic supporter is running to only two ISPs while there are plenty of other options. There are large "just throw your money my way I will set up a classic node" programms that are well funded for the next 3 months. Whether or not you like classic you have to see that this is an inflated count that is not sustainable. The number of nodes alone is also not important. If classic wants to succeed it needs nodes, miners, merchants, users and developers. [1] https://bitcointalk.org/index.php?topic=1380642.0I have seen a number of threads on places like reddit with instructions on how to run a Bitcoin Classic node, that often includes a specific VPS provider. A couple of other things to note: -I would never run a full node from my home internet connection, as I use a laptop with a wireless connection to my router, and I do not want my ISP to know that I am involved in the Bitcoin world I cant judge how successfull this will be based on your actions to prevent this, but I would say its not common. -Even if the above were not true, there were multiple instances in which entire large neighborhoods were effectively cut off from the internet due to DDOS attacks on XT nodes, so large block supporters know that it is ill-advisable to run a Bitcoin Classic full node from their home internet connection.
I see the claims, but I have yet to see any believable reports on this. -Over the long run, it makes more sense to run a full node from/via a datacenter environment because of the resources available in data centers that are not available in a home environment -- it also makes little sense for a "normal" user to really need to be running a full node, and no "to enforce the consensus rules" is not a valid reason because other nodes/miners can simply follow their own rules if they so wish
I myself run two (soon one) nodes on VPS. I know the benefits of a server vs. a home line. It is odd that all seem to pick the same ISP though esp. since its amazon, which is not cheap and not easy. Its way easier and cheaper to find a local ISP offering a small server and following one of the billion guides how to setup a node. Depends on what you define as "normal".
I see this thread has been moved to Altcoins. Is classic now considered to be an altcoin?
Kinda, yes. Based on the way classic would fork theymos thinks classic posts should be in alt.
-snip-
Script kiddies are not DDOS'ing the likes of XT and Classic nodes (and companies that support these proposals).
No, the attack is done from a paid bot net operator according to a reddit post. Judging by the number of IPs I see with the "why? fuck u thats why" subver on my nodes, it makes sense. -snip-
My main point was that there are threads out there with instructions on how to run/start a full node with Bitcoin Classic that includes instructions on how to sign up with a particular VPS service. A Bitcoin Classic supporter may wish to put a small amount of their own money where their mouth is and follow these instructions on how to run a full Bitcoin Classic node.
I would argue, counter to what the OP is implying, that if a very small number of people were running Bitcoin Classic nodes then they would buy up multiple VPS's across multiple data centers and IPSs, and geolocations.
Can you link me one of these threads please? I assume its some reddit thing I cant find shit there. |
|
|
|
|
Looks like a brute-force attack. Maybe theymos did not limit the number of requests.
|
|
|
|
after i upgraded to the bitcoind latest version 0.12.0, the i set paytxfee = 0.0001 on the bitcoin.conf as like previous version. and restart bitcoind. but the transaction fee was very low as 0.00005xxx. how can i set the paytxfee on the version 0.12.0 as like previous version.  Its per kbyte. ok , if paytxfee is set 0.0001 and transaction is smaller than kbyte , the transaction fee must be 0.0001 . so i think minimum transaction fee must be 0.0001 btc. but it is not on the version 0.12.0 AFAIK this isnt new in 0.12. If you set 10k satoshi per kbyte and your TX is 250 byte it will pay 2.5k satoshi as fee. Thanks ,then if i want to set minimum fee to become 0.0001btc, how can i set ?. Because i think fee have to be more 0.0001 to be confirmed quikly. It depends on the size and network load. If there is no solution to this (none that I can think of, maybe shorena may have one), the best solution is to use floating fees[1] with a -maxtxfee=[fees in total]. [1] https://bitcoin.org/en/developer-reference#estimatepriorityId go with estimatefee[1] just keep in mind that it can return -1 which means it has not enough data so you need to catch that if you are issuing payments automatically. If you are using the GUI it will not let you slide to 1. [1] https://bitcoin.org/en/developer-reference#estimatefee |
|
|
|
So, noch 14 Wochen im Rückstand, aber es sieht wieder alles gut aus! Alle BTCs wo ich sie sehen kann  VIELEN Dank für den Support! Woran lag es, dass mir die BTCs die auf den "Change Adressen" liegen , nicht in meinem Wallet angezeigt wurde.? An dem alten Back Up? Ich war "voll" synch mit dem Wallet. Jetzt werden mir die "Geisterbuchungen" in den Transaktionsdetails auch nicht mehr angezeigt.. Change Adressen sind nicht gelistet weil die wallet nicht möchte das Du sie anderweitig nutzt. Wenn Du eine halbwegs aktuelle Version hast, kannst Du sie aber trotzdem sehen indem Du CoinControl aktivierst[1]. Danach hast du im "send" tab einen "Inputs..." button. Wenn Du dort auf "List mode" klickst erscheinen einige Label mit "(change)" und daneben solltest Du die gesuchten Adressen finden. [1] (ggf. sinnvoll übersetzen) Settings -> Options -> Wallet |
|
|
|
I can offer collateral in the form of some cash offhand, either venmo or paypal that you send back upon receiving the total bitcoin I receive. The order is for $750 worth of bitcoin and I have $780 worth coming in, the amount being above. If you are interested please contact me at mitchell_gross@att.net, I know it is a new account and may not seem legit but I am trustworthy and you benefit with this transaction. Thank you Yuck, easily reversable collateral. Im out. |
|
|
|
I don't want to support troll hardfork attempts like Classic, should banning every time I connect to Classic nodes help Core in some way?
After the fork they will most likely get banned as soon as they try to relay blocks over 1 MB to you (someone that actually read the code please correct me if needed). So Shorena, they may be banned by pereira4, but is that not the point at which the Bitcoin network splits in two, as all the classic nodes accept the larger block and the core nodes are still looking for the next block? The network is split with the fork, yes. One side is accepting blocks over 1 MB size (up to 2 MB) while the other side is rejecting these blocks as invalid and will ban nodes that consistantly send invalid blocks. Its most likely not an easy cut, but more like a messy tear as some blocks (those smaller than 1 MB) will still be valid on both sides. Due to the 750/1000 blocks needed for activation and the grace period it is however unlikely that there will many core nodes left afterwards. |
|
|
|
Imagine that your nodes get DDOS at home so people move to free and cheap cloud based services to keep them up.
Imagine how actual server operators easily mitigated the DDoS attacks[1] as they are primitive and flawed. It also makes no sense that every classic supporter is running to only two ISPs while there are plenty of other options. There are large "just throw your money my way I will set up a classic node" programms that are well funded for the next 3 months. Whether or not you like classic you have to see that this is an inflated count that is not sustainable. The number of nodes alone is also not important. If classic wants to succeed it needs nodes, miners, merchants, users and developers. [1] https://bitcointalk.org/index.php?topic=1380642.0 |
|
|
|
I've removed all the posts that contained bad advice, as it will risk your wallet, and that's not something I can agree with. If you want to complain, feel free to do so in Meta.
Thanks. If you want to use the same wallet over different systems use a HD wallet like Electrum or Multibit. They can mitigate some(!!!) of the risks Danny is talking about. I would say - even with an HD wallet - its not a good idea for different people to use the same wallet on different systems as there is always the chance that both create a transaction that spends the same coins at the same time or very short after eachother. If you are however using the wallet alone I see no issue when its available on different machines, besides maybe that its more likely to get compromised. |
|
|
|
hab dir dann mal geschrieben aber ohne PGP...finde ich dafür nicht so notwendig
Alles klar, ich gucks mir nachher an. |
|
|
|
But is it normal that it takes hours to go from "4 days ago" to the current one? I mean its just only 4 days, how many mb can be that? As far as I know they have made Bitcoin verify the blocks faster with this update, but it's still as slow as ever for me.
What I noticed is it's a lot faster when you open it, but now then synchronizing.
Bitcoin network on average, generates roughly 144 blocks per day. Multiply that by 4 and it would be 576 blocks. On the worst case scenario when the blocks are filled to the brim, it would result in 576mb. Even though the verification is improved, quality of your connected peers, internet speed and HDD speed remained unchanged. These could cause a bottleneck. Yeah I should update my hardware, but I can't now, no money. If I had to choose, what would be better, more ram, an SSD, a better CPU? what's the priority here? I've got an old quadcore, a regular 7200 RPM hard drive, and 4 gigs of ram. Unless you are several CPU generations behind I dont see a reason for you to update yet. As long as the machine runs 24/7, is well connected[1] it should do fine. Even if you shut it down over night you should be fine. You obviously cant expect from the machine to have core up and running within a few minutes as with a modern CPU and an SSD, but I dont think its unreasonable to run a node on an older machine. Keep in mind people are still using RasPis to run a full node. Your machine should be way faster than a RasPi. Edit: [1] try adding addnode=188.68.53.44:8333
checkblocks=144 #0=all; default 288
checklevel=2 #0-4; default 3
to your bitcoin.conf. This will make you connect to my node (and others) so you have at least one connection that can provide blocks quickly and reduce the time needed to check blocks on startup. |
|
|
|
I don't want to support troll hardfork attempts like Classic, should banning every time I connect to Classic nodes help Core in some way?
No, until the network is forked classic nodes behave very similar to core nodes. After the fork they will most likely get banned as soon as they try to relay blocks over 1 MB to you (someone that actually read the code please correct me if needed). What would happen if everyone running Core banned Classic nodes from connecting to them? I just don't want those leeches anywhere near me.
If everyone would refuse connections from nodes with a certain subserv, they would form a separate network. This could easily be mitigated by changing the subver though. |
|
|
|
The policy to not remove anything worked when the forum was small. Now that we have thousands of posts a day, we can't afford 50% of them being junk. The moderators are now instructed to be less tolerant of low-value posts.
Some guidelines:
1. Free speech - you can say anything as long as it is relevant and presented in a calm and polite manner. Swearing, SHOUTING etc. make your post more likely to be removed.
2. No zero value posts or threads, like "SELL SELL SELL"
3. No pointless or uninteresting threads.
4. No referral code spam
5. No NSFW content
What should be the minimum number of words in a given post. Just to be sure I do not fall into the category of "zero value posts." Quantity has nothing to do with quality. The above question about when a user is able to post images could have been answered (in a constructive manner) with 3 symbols ("Jr.") IMHO. |
|
|
|
Can i stake mine? https://keybase.io/mocacinno/key.asc-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: Keybase OpenPGP v2.0.51
Comment: https://keybase.io/mocacinno
xsFNBFbxKHMBEADGM3Dbd9/P+W1rSDN1RPfDSwXdd9QwTiSim7Yhe3v3azcXJltO
vzQezZ0Fy5RFUB37qhz0upZ31xJ8CAr0jN6bmJgusmygoY+YfqfFjkjAc+Inr69m
fKBNW8Ip8fFShWiceK+2hMX9VkRxf+CyYzq9nmUplz9qxZZNv+xYY9XTMQWjqv7X
43LNr6b7VOkLCbww7E28RCEi+9EVTPXj7t1q42oEiAPX3QJGsfLiyGGZMWCMrSM3
p4FPEJ2JRSd314QEfXBl0wwytln0/BfRwcGg5mkYP+sls4FwCmvm3d1SE6lYeTQn
FWQtLHXDfWMRLO60b8u1kMleUrPivBEglfLKT1PGUVg+7HlLDDUw/z/ue5hqxrdg
VUF6XolndWY8NB9Ciu5FzvQHuLRaYJSwucqSAEPMA1U+eDSbCz1dgZitK4s99Rz5
aXWlOCxcHOxHaq0zk9mO/tfpJ/pLTbWWv0Vg6UoIwqr+9Yi2qAHfbzrITR4Z3jy7
jir8ZtOFH4Jbb57t2rQ8+ToC9wijU+e64ahTV5h7ZjexAQ4mCncxNNlaiOwHHM1O
aqdPO52+DABPrSUnUImQAreidHOBEIfat5B1G2wHa71FqZbOO2Onm7+xuL5Attgm
RfekbTv3Qd64DIl3M6xT7fax5pXCS1wyU2Aa3BWybwaDOhtvAgXM4IBV3wARAQAB
zR1tb2NhY2lubm8gPG1vY2FjaW5ub0BnbXguY29tPsLBdAQTAQoAHgUCVvEocwIb
AwMLCQcDFQoIAh4BAheAAxYCAQIZAQAKCRBavUGiVYizzcBlEACceD8u9+O5WnUf
WVm9CYehvoULHXNPyPReX593IAhSGcMX67eMk6pt6u3ErFg85xPqwLcmwGlScE/k
mrlrD+wLFgpRGxtKIVeeES7Y97NJpAKQXgj3a73AWlyBYEaW3G+nGvntCprDeOV6
tIGx+BpK489teEykuf+IXpxEfmdOTzqRlxgFjyvv6U97iqrbd8uy46pow6/VtakG
k7xrkN83L6hPP4klqgFHEWgx2GANi6KAxtGFdYTCNplT4zV0CFFwmdW1MsY15QNf
whnAffPgjo8CPBXUbSmA0bSItPF0XqTAxDYlmKKspdFM4dCyYBw86wj9pb+B+L2J
3+ZZ2jWYd3kMeyx0mF+m4YcH38BiYsIq+ZjcjiU1Ciq9fHDmCqqux58q7FJGfsrl
FpO5uayhwvOnP/d2ZGd+ozxGNE89g/aA+dS+6v8Diwz8qqVj+WxeXi5XBGkyyVax
HRBVaoedSqP8ghF5wCvIoga5NA7IJWRv8LTUnaG90dCcsVf49/UoLdxlgEbPS59C
hiVro0ct19NFTjWsYhKYEcu7xoEgMXBwPQCZ83W0c6zRdDTx5uCCc9M2F5EgB/YP
5DfN/0g/ud4VtGplQy6pnsHOnxAELs4Pe2DRryHfs285IQsAaWIzPuVeW4poSrTn
yeYBEAjCubohNOhzhEZ+aLdJ2PcWhc7ATQRW8ShzAQgAyZ8ddSLfDLIcrGam/3qP
j2kz8RLa69kWEvwtn/tyy1ce9HYpt+MoII82RXyfa8z7AXrR/NTZIDZtSgWyeP8m
7IvrEh0aK544Das8L69gzGVKbiTaihMn6NZfEAqcPTa5eUEZAubbdyBT3U6yPD3K
ab9lISdvB+2bkx4SDCqt6FRPApH3TzcFumCOwbfwQb6HfDhZmgXGqDO/k7k5ZlT9
p4tD1LSfCFlLTRtqYErY29hFU9icrrstCOJURDWtoFFY42Z2c+dYDFviEmNCrJmO
/bWVZbhDqWEKScxPecPLacGmh8od3k04GOz9+ikRAwANiRcIVxcyodvXohvvunCD
gwARAQABwsKDBBgBCgAPBQJW8ShzBQkPCZwAAhsMASgJEFq9QaJViLPNwFwgBBkB
CgAGBQJW8ShzAAoJEEaH8AWroZRG/VAH+LYqN/u4iYpdA9Sz/pn0HcEbHfht/U0G
Xc9LBSMBG29gwFC5OydO2GlaVafBDPsiiJyadzY67COzFkl1G7J/dqYR5S/SDxn7
FukriTm6nYuoYLT7a1eaLrYfaMtFI/zEi1UKiqtO6fTtr+z0yvgNm2OGHDA2tTi7
4WyovmChbPcpyxS8ZjI4J+oJn/WOtMI5qZjRY9LnUaYVW+zl3U1Mt3/YhJ5GhoSV
3/EA6WhUYZHawuEMbh+drEE3w0uDYhhPgOyvqvam9eStfLvgcvt3++ZVQ0zi2Mdj
uuPOPC3C8t336M3/HsNFMhFbqwgy4PXBJ9UmTGZ0sXzXkMxjVQAFkPH3D/9pMN+Z
i7iYMtB6EDG1F32o2VQBPk1TZ7AinVPQpk90vjrtLNaeE+tjqqkjFhSW1pX3AxmI
nKn5PPGuyIcrRyi9Rm/yXjwLw+NHcLBjSreAmJJggBvIBctSF6OuHXQ0xdgdMpnm
/HL6l5tEtLECIVWFtZlrO3+AkFVq09zm/Bbh8oR8vpsnEydmqkNoGk/1CVuhDJi+
Q8sYWLt3jHZa//va9YdGXZdofi4GUpAhOlYK9eJ3+StiajAOmKfE+o9VJfX0Aut+
/A/Pud0BxvU1hlWI7dh3Z9RJh9yhoi1z5l/RuMtt6PsuD7TXWl2Jy24OZqtYVJif
NEcAlRKVbut3jx+GvltpLA8W0Ze260MKqn5+bIUDyKiHjLRfqeVbRk6gqlfLiShS
uTdn7BZ9oobtjDVzix1t1Yn1ZBdqB4h00rHEBwdDQJXQWhtAGYQ0EVraar3CFDsT
LZGpLVn1oYkkyqzSASlS0BJHpvzvIolQvTSCzw5FmcqH2KX6A8PI0ATDehoQCWl3
34r263+LRJwOh3Sh3KJAg+BMiLtWpLjysc9+bVi3UOejIk9qdZ6NtmaAhhK3HipB
nB7j/gpGMytOZt0LmgbKh6/REGqtH9j39S2e6oSBoZz/sYNTgAm6CqDoC6y4iMgI
lBiEJseGyKGGwD8+kjcXbxVSi0OrY7RZji5VcM7ATQRW8ShzAQgA5IHAV5nYdrcC
iFQhPXjRyx9xIWI1Avav6yLWRFEuwox24AfydMtFy3ssdGP1TH3JfyLDNkb3m9w0
2N030lqFEwLyNl8avjs0BDXZGHaJfeR2xuJhoOdokhsJL7hk0lDcf9eHYKC7RxnH
cfCBzH/5ILC1LNQXIlDEVdUXIoT+Vf5Z/ST+Mpe3Y3xri6Z1e7UwMO48Yxx+l7Ak
P79og0g+OEczQI5AIl2gE1T+2vtEThkUmnEFyaWK6PLMxhVf91m7yB4PhvVA/2dh
QDmJ2gm1iaLoq+P8FQ2OXT5PBag03GrATesx7fiELSavmCaa2H+TeKz2st7+uB6Q
tpjPRSZHxQARAQABwsKEBBgBCgAPBQJW8ShzBQkPCZwAAhsiASkJEFq9QaJViLPN
wF0gBBkBCgAGBQJW8ShzAAoJEGGXYrgP8NsjpxwH/R3OsV//3uu9ltvqm5P9FKKR
J6UsM7yWvqI2VZyVF4RI65cH8aJlQLYFy8OYZE+SQ9uHWPa0KOo50i8m/llOrnrS
+WNJAVeFEcC5t4NBcokQ/yvuVa7T7bG0+jtNrgRh/ZVtzWZ+AE0tE2cKnNobT3NS
t2j7DGnUOM57Ki902W8IyaodskXfA79DwzJsui2zeshe6Aim7MkTwTvwZWZ9Ou56
T0NxNzWUlSLA3PiNFffqc262llwcRD/iwuUqo245VthzKijZ0K479wO2tfs4PzXf
KgO2Nzi2u3MI3cdlNW9ZQAC6Ih+/KJw5iFnvkyX/3TWzSop7ZlaRoZPLhHz/Sb9H
rA/+KXPahusISW4blmUGTK2Pg17Uja3cUk2shuHXkTswvO0zD0YD4M78YRTwr736
fzjqZ+KpeMylIwQJeyKJYu+SNgb1ZfZmnDPZ9AMhoZ9iFY5EvvssYNgrdzog6IZw
eNy4v5VwJ48j7YYAKA0nZFR8x/+t4P3n3tBdSegeN5z1woGqJYYRig81BCJkj4mH
iR9LkY9wWOxDqOgNeSNTpR6Mmb7k34yrxSl744d0uv+mux23Wnu/PixM719zIweM
lR2D1OCwbJrSqUYETPRcLZbUtQ4vLauRhQ9eaNLm2iY9ynKPNp236lqFHmQHXCUS
wG7N1ENxgdH3FiIzQYuMC4eP8BdYWKiWXvFSiPPkmJ12rxsWg0cZ+PT39i6MhajM
jx2Shaa8ikZvhsUOA9QHapaMTIqypcN0ChocIZPSxF0mp945t57VFvM/2Pgr7YwU
/jTw7qhwa+bl4vHQdji5YEk+zIgrcm81dw+DYozRNphxzvEtxwMyJLx+Uyaifu+v
kIz0lM8God5gora1mDyj63t2kBvAa5acfwK+q2h7rd0wum9Yxq3LK1x+r7wCKrtq
duePKm0FZnTrFXfUwJj8sLo20GgLDyrUYM8haIZrW6VdurvjsN+DLq/ZGV9emZ24
S7ISYvmc8fbRpYUIaNWBrULOVwj62fkeN3X8xf0U/rMpvtA=
=t1xt
-----END PGP PUBLIC KEY BLOCK-----
fingerprint: E633 2440 C530 8609 9B38 5055 5ABD 41A2 5588 B3CD quoted. |
|
|
|
-----BEGIN BITCOIN SIGNED MESSAGE-----
I have now received the funds from BitMixer.Io - turns out my wallet had stopped synchronising. (My bad)
-----BEGIN SIGNATURE-----
1PYPjneN6iiXxgNEAMdcipQmR4JKcZSJ7F
H1SnZ5nxqsTVxLTkgAFus+DZp+BK17cGjzLFsmL5VGcOWlbzGOLChOfU8nfqwu2MfQhslKz1n/TPimiQhihFd5I=
-----END BITCOIN SIGNED MESSAGE-----
Quoted Wana sign that with your old address 1AhuQTWMu185kWFmiUHhmTTVYjKR7BfirW[1] or did you post in the wrong thread? [1] https://bitcointalk.org/index.php?topic=996318.msg13627395#msg13627395Why would I want to sign with the old address? 1PYPjneN6iiXxgNEAMdcipQmR4JKcZSJ7F is the wallet that was affected? How do we know its still you if you just stake a new address? What... Would one do if one lost access to their old private key? How would they prove they are still the original owner?
You cant, unless you have other means (e.g. other addresses from old posts, PGP key, etc.). |
|
|
|
15XDwUwKJhPQKrU6Q8CH7jXwqQ9n6s2KHt
Please quote. Thank you!
Here you go, just quoted your bitcoin address, hope you know how to sign bitcoin message. MAy i ask? What is the use of bitclin signed message ? I don't know how to do it also putting your bitcoin address here or mine ?may i know of what is its purpose. Thank you . it's explained on the first post of this thread. to prove that you own that address and the account that posted it. also signed message are necessary if you need to recover your lost account. Ok thank you , i wil read it on the first page , i ask if i don't understand , sorry i am newbie here on signed message account .i will post my bitcoin address too . I hope this can help me =) It can only help you if know how to sign a message. If you dont, learn how to -> https://bitcointalk.org/index.php?topic=990345.0 |
|
|
|
-snip-
This account was only created to help on urgent matters, won't be used to trick / evade the ban.
Will be more attentive after the ban expires but wasn't aware that these rules were so strict (seeing from other topics of same kind)
If you think it's appropriate, delete this account / I won't use it more util the ban ends.
It was created to inform our users taht we are banned and to appeal the ban (since we haven't received any email)
Thanks for the time and replies.
Its fine to create a new account to appeal a ban, you cant however post in threads outside of meta or in threads that are not discussing your ban. |
|
|
|
|
Show Posts
