What harm can this do? Isn't this supposedly required... At least when you solo mine? also i am curious do you have RPC allow ip in your conf file ?
Okay... Now you really scaring the fuck out of me. putting all your altcoin wallets in a virtualbox will not do anything to protect you.
You gotta comprehensive list of approved coins? I need that link. first off a LOT of coins allow a wildcard value setting to be used in the conf for RPC ip address's so this is a well known infamous vulnerability we Senior members here know.. some of us anyway  and you don't get what i was saying and sorry i don't feel like spelling it out again.. there is no list of approved coins.. i just said if you stick all wallets in one VM your not protecting sweet fuck all hell your making it easier for one rogue wallet to steal all your wallets LOL try some common sense guys.. Not that I need to remind you... But you're such an ass, asshole - but thanks for the intel  Anyhow.... I had no clue about the wildcard value; I'll look into to how I can mitigate, if it's possible? And I did get what you said asshole. Also I was inquiring about your personal list of approved coins. what personal list of approved coins ? ..i never said i had one LOL and what coins ? none ! Bitcoin that is it. edit: and the RPC exploit was reported to be the cause of the Jackpot coin from users months ago.. some guy went through the list of IP's connected to Jackpot coin and then attempted to connect to them until he found some wide open. And i guess from there he stole millions of coins and then dumped them on an exchange (story on JPC ANN topic) The coin JPC was updated to NOT support the wild card setting anymore but i have no idea how many out there do still support it. I had always used a loopback address so i dunno if that is maybe safe instead ? Whateva Spoetnik - I didn't say you said you had a list; I give you credit because you gotta knack for picking out the shitcoins, that's all. But bump you... guess I'll just have to go thru your post history to find out which coins you call out. And to think I was going to vote you as the biggest retard here... not!  |
|
|
|
Ok, that's a cool ass map. But damn, 52 in one month!!! This shit has got to stop! |
|
|
|
|
Wow... This was clever.
I had to go letter by letter just to figure out what the hell he did. The scams never cease to amaze me.
|
|
|
|
Example 2 for believers : % Chance to win : 95 %  ?  Damn Soon as you raised your bet, bim! That's how they get you. People who claim these games are fair aren't telling the whole story. |
|
|
|
What harm can this do? Isn't this supposedly required... At least when you solo mine? also i am curious do you have RPC allow ip in your conf file ?
Okay... Now you really scaring the fuck out of me. putting all your altcoin wallets in a virtualbox will not do anything to protect you.
You gotta comprehensive list of approved coins? I need that link. first off a LOT of coins allow a wildcard value setting to be used in the conf for RPC ip address's so this is a well known infamous vulnerability we Senior members here know.. some of us anyway and you don't get what i was saying and sorry i don't feel like spelling it out again.. there is no list of approved coins.. i just said if you stick all wallets in one VM your not protecting sweet fuck all hell your making it easier for one rogue wallet to steal all your wallets LOL try some common sense guys.. Not that I need to remind you... But you're such an ass, asshole - but thanks for the intel Anyhow.... I had no clue about the wildcard value; I'll look into to how I can mitigate, if it's possible? And I did get what you said asshole. Also I was inquiring about your personal list of approved coins. |
|
|
|
Another option, if you have Linux/Cygwin/(probably)OSX, you can search through all of the extensionless files recovered by Photorec and use the `file` command to determine the type. Wallet files appear as "Berkeley DB (Btree, version 9, little-endian)", and so you should be able to find it relatively easily by running something like `file ** | grep "Berkeley DB"` (if you have globstar enabled, though there are many other ways of recursively searching every file within a specified location). You can use this technique for other file types as well, though anything plaintext will simply show up as "ASCII text" so it'll only help for binary file types with a specific identifier such as PNG (though presumably Photorec handles much of this, given the name).
Yeah actually that's a very good idea. And you can simply do (without globstar) find ./ -type f -exec file {} \; | grep "Berkeley DB"(And replace ./ with the directory path) I'm getting this error back: find: missing argument to '-exec' I guess something's missing from the line? |
|
|
|
What harm can this do? Isn't this supposedly required... At least when you solo mine? also i am curious do you have RPC allow ip in your conf file ?
Okay... Now you really scaring the fuck out of me. putting all your altcoin wallets in a virtualbox will not do anything to protect you.
You gotta comprehensive list of approved coins? I need that link. |
|
|
|
spreadcoin/src/main.h:832: unsigned char pchMessageStart[4];
[...]
spreadcoin/src/main.h:1564: unsigned char pchMessageStart[4];
spreadcoin/src/protocol.cpp:20:static unsigned char pchMessageStartTest[4] = { 0xc2, 0xe3, 0xcb, 0xfa };
spreadcoin/src/protocol.cpp:23:static unsigned char pchMessageStartSpreadcoin[4] = { 0x4f, 0x3c, 0x5c, 0xbb };
spreadcoin/src/protocol.cpp:25:void GetMessageStart(unsigned char pchMessageStart[], bool)
spreadcoin/src/protocol.cpp:28: memcpy(pchMessageStart, pchMessageStartTest, sizeof(pchMessageStartTest));
spreadcoin/src/protocol.cpp:30: memcpy(pchMessageStart, pchMessageStartSpreadcoin, sizeof(pchMessageStartSpreadcoin));
spreadcoin/src/main.cpp:3263: unsigned char pchMessageStart[4];
[...]
spreadcoin/src/main.cpp:3585: unsigned char pchMessageStart[4];
[...]
spreadcoin/src/main.cpp:4389: unsigned char pchMessageStart[4];
[...]
spreadcoin/src/protocol.h:62: unsigned char pchMessageStart[4];
spreadcoin/src/db.cpp:496: unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb };
[...]
spreadcoin/src/db.cpp:536: unsigned char pchMessageStart[4] = { 0xfb, 0xc0, 0xb6, 0xdb };
[...]
Cheers Graham Figure I might as well get my coin's worth. So I just read this thread from beginning... To include the info listed in the code Graham listed. Mr Spread, what's that line of code in your db.cpp? Why would you need two different pchmessagestart identifiers for a coin? Which one is your coin's network? |
|
|
|
Seriously? disappeared... and even pulling my last active date? You know... I'm not even upset that I 'lost' this bet, but assuming I disappeared because I wasn't active for a couple of days is silly; if I didn't know any better, I'd think you're trying to piss me off. Surely you took a peek at my post history... I don't post here everyday; I have a life. Actually, I never log out so it should look as if I'm logged in 24/7. The only time I log in is when I have to restart my system or the site goes down. I need to fix that anyways. I did't mean to offend you, this forum in fact showed that you were offline so it appeared to me that you had logged out shortly after my post. I didn't go futher to explore your post history. Anyhoo, your choice... you can start a new thread that you won the bet and I owe you (frankly, knowing this tidbit is worth a coin; I've asked several devs for it... most had no clue what the hell I was talking about) or we can use this thread for your payments. Yeah, I'm gonna pay you, but I'll be damned if I'm going to assist with funding your endeavor; I still don't have much confidence in the success of this coin. On the other hand, if you were an established member, they would've been in your wallet shortly after I logged on today. I don't think there is a need for new thread as there is not much to discuss, you will pay when you can/want. For your peace of mind I can assure you that I would continue to work on my cryptocurrency regardless of this 1 btc, so you won't actually fund my endeavor. So Darkcoin is also a scam in your opinion: https://github.com/darkcoinproject/darkcoin/blob/master/src/main.cpp#L3591 As well as Bitcoin: https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L3214 As you said, these values are used to identify the network. They are the first bytes that each node sends during a connection and they are the first bytes that each node should receive. This way you can easily detect if you have connected to a wrong cryptocurrency network (or even something completely different like a webserver or bittorrent client). Wallet cannot work without these values, they are not specifically for pools. Pools also need to connect to the network so they also need them. For SpreadCoin you can find these values in protocol.cpp: https://github.com/spreadcoin-project/spreadcoin/blob/master/src/protocol.cpp#L23 Note that values that you pointed to in your screenshot are actually for testnet. My bitcoin address: 1MSL9Ph2RCUnpekpuf6Rofb4kUo1nArsnS Of course I don't think that either is a scam - but I see the link indicates those values are in their main.cpp file - yours on the other hand is located where people who write guides (and even on the wiki itself) neglected to tell people. Now I'm really wondering. I don't claim to be any kind of techie, but using their instruction, I was able to create the network.py files for the coins who didn't have them listed in the hub. It wasn't until I started to bring nodes online for these fly by nights that I noticed those values weren't in the main.cpp. After asking several devs how I can find them and got nothing but crickets, I came to the conclusion that something must be up with it. Before downloading the files, I always checked the files for the values needed to bring a node online... there was no need to waste my time compiling a wallet for a coin I couldn't set up a pool for. But like I said... this info is instrumental; worth a btc IMO. And yes, I realize the numbers were for the testnet; the hex value for the real network is located in that file as well. For DarkCoin these values are in protocol.cpp, for Bitcoin they are in chainparams.cpp. But all aside - I have no problem paying up; I keep my word. I'm just curious to know why all the instruction provided by members (on this forum, github and others) all point to the main.cpp for the pchmessagestart value. No one has ever hinted that it's listed in a protocol file; this has me wondering whether there's any significance. Technically it it possible to put them in any file. Maybe for most coins these values are in main.cpp but main.cpp is bloated with many unrelated stuff so devs try to move some code out of it. Thanks for the info, but I'm still going to dig into it; I don't know the first thing about code... I simply followed everyone's direction to start a p2pool, but this is an excuse for me to learn about coins on a deeper level I suppose. Don't take me very long tho to learn tho - hell, it took me less than a month to convert my rig to a web server and build a website and I knew absolutely nothing either going in. Still can't figure out that damn mail server, but I'll get it right. I'm more focused on learning how to harden the system more than anything right now; silly chick had her box wide the fuck open, no wonder it went bunkers on my ass and I lost everything. Anyhoo, until I recover my wallets I'll have to buy btc - the coins I have at an exchange are already reserved for the person who helps me to recover my files. |
|
|
|
Well hopefully she (thats what here profile says anyway) will keep her end of the bargain up!!
And when you get sometime would like to have a chat with you maybe on a IRC channel or something , I know real world can be busy , but like I was saying , I see a massive potential here and want to have a chat, when your available!!
And she (yes, I am) most certainly will. And what difference does it make whether I'm a female or not in this situation? You took the time to view my profile, so I wouldn't doubt you skimmed my previous posts. What, not used to a girl not begging for coins here? I do apologize if that sounded sexiest , I should have done it as a edit as I originally wrote he but thought I would double checkand changed it my bad!! Also I have many female friends in the crypto community and quite often they will bring a fresh view point to the table so no I really dont have any problems with females or girls!! But if I offended you , sorry!! Goodness! Now you're really being sexist by thinking that I need an apology But no, you didn't offend me - I just thought I'd point out that bucket you placed me in, that's all. |
|
|
|
Evidently you assume I downloaded the files? But since you seem to know what my problem is
Not sure where you get that notion from, I was pointing to a pure-text solution which would eliminate any need to use/upload images<- the problem. I thought it might make that particular task a bit easier to manage. Cheers Graham Ah! I see what you did. I assume you were hinting that I didn't know what I was doing because it took a minute to upload the screenshots. Yes, your method would've been much if I actually had the files downloaded - I was just using a browser's preview pane. But I wasn't being factious about the offer to assist me in recovering my wallet files - I'm still on the hunt. Unlike the incremental payments mr spread will get from me, I do pay out my bounties in full - and I don't retract them. Hell, I still sent out a mobo even after I found it was working - I held a give away for a free broke mobo; turned out it wasn't broken after all, but oh well |
|
|
|
Carry on... so subscribed |
|
|
|
Another option, if you have Linux/Cygwin/(probably)OSX, you can search through all of the extensionless files recovered by Photorec and use the `file` command to determine the type. Wallet files appear as "Berkeley DB (Btree, version 9, little-endian)", and so you should be able to find it relatively easily by running something like `file ** | grep "Berkeley DB"` (if you have globstar enabled, though there are many other ways of recursively searching every file within a specified location). You can use this technique for other file types as well, though anything plaintext will simply show up as "ASCII text" so it'll only help for binary file types with a specific identifier such as PNG (though presumably Photorec handles much of this, given the name).
Yeah actually that's a very good idea. And you can simply do (without globstar) find ./ -type f -exec file {} \; | grep "Berkeley DB"(And replace ./ with the directory path) Sweet!!! Will try this next |
|
|
|
Did you already get your wallet data back?
I had this problem as well, using a simple recovery tool. Anything should work really.
I hope you get yours back!
Thanks! I haven't yet, but here's hoping! |
|
|
|
Try Recuva recovery software and search for wallet.dat or just type .dat you can search it in specific participation, you can also search for any other format you need for.
I think I tried that - I think it's only for Windows. But even so, the majority of the files I recovered extension was renamed to .txt. |
|
|
|
My main account (minerpools) was just banned for 7 days, just for posting one liners to let people know when a pool was up.
So, mods, if you're going to charge a fee, do it, but be clear about it, don't start telling us we can't do our job for no apparent reason.
Same Here (hashlink) but I've got 14 days ban  If I try to register another account there is "fee" in BTC ... Nice, a What the hell are you talking about? if somebody has too many accounts from one IP or uses ie TOR - he has to pay to get in Ah! Didn't know that... maybe the original account I created is actually worth a few coins I actually forgot about it until I tried to change my email address last week and realized it was already used, lol. Hell, it's almost a year old with no post history. |
|
|
|
We need more miners of this coin. It is a good coin: no premine, fair launch, still solo-minable by wallet.
Would be nice if some pool (or the Dev) would be able to adapt some miner code in order for it to be minable with pools. It is X11 with an adaption in the timestamp code: 64 bit instead of 32 bit. Any poolowner around that has the skills to work on this?
Not possible. The hex values needed to identify the network is missing from the source code: SCAM COIN ^ obvious shit/scam coin called Spreadcoin or something... I couldn't resist, lol. It took me less than 2 minutes to navigate over to github and peek into the code. My coin is not a scam. This method for detecting scams is flawed: 1. You search for these values in main.cpp. For different cryptocurrencies they may be in different files, for example for SpreadCoin they are in protocol.cpp, for Bitcoin they are in chainparams.cpp. 2. This values are not only for pools, they are necessary for ordinary nodes. If wallet source code is released then they are available to everyone. For everyone else who is interested there is discussion about this (with me and Lucky Cris) https://bitcointalk.org/index.php?topic=715435.100Ah, following me, I see. chainparams.cpp isn't used by any new coin nowadays. But it seems that one dev placed the network's hex value code in some obscure file, that that even the people who provide instructions on how to start p2pools don't know about. I wouldn't doubt that the coins where they're missing from main.cpp and found in protocol.cpp are all just clones of that one coin. I'll say it here as well - I still don't have confidence in your coin. Actually, I have none. Your ANN has nothing special... nothing that would make me think that spreadcoin will maintain a permanent position in this scene; hell the only people who seem to be mining it are newbies like yourself. |
|
|
|
I think all of those accounts that instantly support a new coin and defend the dev are the dev's sock puppet accounts.
What else can we assume? In particular the n00bs, who just seem too overly excited about a coin when there's nothing to be excited about. |
|
|
|
My main account (minerpools) was just banned for 7 days, just for posting one liners to let people know when a pool was up.
So, mods, if you're going to charge a fee, do it, but be clear about it, don't start telling us we can't do our job for no apparent reason.
Same Here (hashlink) but I've got 14 days ban If I try to register another account there is "fee" in BTC ... Nice, a What the hell are you talking about? Yeah, what he ^ asked. |
|
|
|
So Darkcoin is also a scam in your opinion: https://github.com/darkcoinproject/darkcoin/blob/master/src/main.cpp#L3591 As well as Bitcoin: https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L3214 As you said, these values are used to identify the network. They are the first bytes that each node sends during a connection and they are the first bytes that each node should receive. This way you can easily detect if you have connected to a wrong cryptocurrency network (or even something completely different like a webserver or bittorrent client). Wallet cannot work without these values, they are not specifically for pools. Pools also need to connect to the network so they also need them. For SpreadCoin you can find these values in protocol.cpp: https://github.com/spreadcoin-project/spreadcoin/blob/master/src/protocol.cpp#L23 Note that values that you pointed to in your screenshot are actually for testnet. My bitcoin address: 1MSL9Ph2RCUnpekpuf6Rofb4kUo1nArsnS Of course I don't think that either is a scam - but I see the link indicates those values are in their main.cpp file - yours on the other hand is located where people who write guides (and even on the wiki itself) neglected to tell people. Now I'm really wondering. I don't claim to be any kind of techie, but using their instruction, I was able to create the network.py files for the coins who didn't have them listed in the hub. It wasn't until I started to bring nodes online for these fly by nights that I noticed those values weren't in the main.cpp. After asking several devs how I can find them and got nothing but crickets, I came to the conclusion that something must be up with it. Before downloading the files, I always checked the files for the values needed to bring a node online... there was no need to waste my time compiling a wallet for a coin I couldn't set up a pool for. But like I said... this info is instrumental; worth a btc IMO. And yes, I realize the numbers were for the testnet; the hex value for the real network is located in that file as well. |
|
|
|
|
Show Posts
