i am new with CLAM but i really like this coin, now i sync my client please advice- its any way to i can simple add my bitcoin private key to CLAM ? (in client i saw i can import only wallet.dat - its not possible to import the bitcoin private key) thanks
You can do it via the console. Use importprivkey with the BTC private key. Afterwards you have to restart the client because for whatever reason the tab for receiving addresses does not get updated, and the console gives no hint that it was successful, or what CLAM address was generated.
|
|
|
Repost from a thread that has been deleted:
Imho, it's a joke. After being a member for over 3+ years now, I earned an amazing $0.14 in BTC, at about 4 Satoshi per day, with some bonus. Without bonues, it's currently 0.00000002630 BTC. Yes, they use 11 digits instead of just 8, so at a first glance balances look more impressive. If you want to withdraw, you have to exceed a certain minimum amount. For BTC, that's currently 0.00015. Remember, at 2.63 Sat/day. Oh, and let's not forget the transaction fee of 0.0005 either.
So, to send the minimum of 0.00065 (0.00015 + 0.0005 fees), you just have to wait 24715 days, or almost 68 years. Now you do the math for how long it takes even if you somehow manage to earn a 1250% bonus. Hint: it's still years. And then you earned how much? About $0.50.
For all the other coins the daily dose is similar.
It's more likely for the website to vanish before you manage to withdraw anything.
|
|
|
It was around 760,000 BTC, now you do the math.
That said, even with Trendon Shavers in jail, there are others who got away, like Ian Grice.
|
|
|
I'm using DECIMAL for storing values, and so far that worked fine with calculations in SQL. If you want to do math in PHP, you should look at BCMath.
|
|
|
How are you going to sign a message if you're not willing to use a website or some software?
Well, okay, I give it to a software, namely one on the airgapped system. Maybe this is the part you're not understanding. What do you mean about "giving up my sig address"? Do you think that when you sign a message with an address you aren't making the address known? Because you are. Every time you publish a signature you are publishing the public key along with it.
I was referring to the vanity address in my signature. If I'd use some website which claims clams by using my private key, that address would essentially be dead. And I want to actually keep it because it's well published. Signed proof is how every transaction works in every crypto. If you're looking for a way of signing a message without revealing the address used to do the signing I don't think you're going to find it.
With Electrum, you can have two wallets, one with the private keys on an airgapped machine, and one with watch-only addresses on a connected one that does not contain any private key. You can create a raw transaction which you can transfer to your secure machine, sign it there, copy the signed transaction back and broadcast it. That way, the private key was never exposed to the potentially insecure machine. You can even copy that signed tx to a pushtx website, like at blockchain.info.
|
|
|
My suggestion is that maybe is possible for you to set up a clean OS where you can install the Clamclient and let it fully sync with the clam blockchain, maybe a full sync won't be needed because I think since the undug clams were assigned prior the Clam blockchain started running, those clams must be at the beginning of the Clam blockchain (but at least you will need a few blocks in your clam blockchain), then you can unplug/block/disconnect it from the Internet from your freshly installed OS, import your btc/ltc/doge wallet, check how many Clams you got and them create a transaction and sign it with you Private Keys, you will need to create a receiving address and properly make a backup of it, so you don't send your Clams into oblivion.
All this done without Internet connection should protect you from the possibility of your Private Keys being sent by the software to the Internet, then with the transaction saved in a file you can find a way to decode the transaction, there you can see if there is something wrong with the code or signature, then you can push the transaction to the clam blockchain and your transaction should be mined and validated, usually you'll have few option with clam to push your transaction, you can make another Clean OS and this time I think you should have to fully sync it, so you can push your transaction or you can ask a friend with a sync clam client to push it for you (coz as far I know there no risk for your Clams to be stole by being push by other person).
After all that, you need to properly delete your clean OS (the one were you put you btc/ltc/doge wallet) so you don't let any possibility of your Private Keys being compromised, Probably occupy the Entire disk with new data and proper format should do it.
Thanks for the thought you put into it, but it would still mean that I give eg clamd access to my keys (in a truly paranoid way I could argue that they might be added into the transaction as eg comments). Ideally, Clam would allow me to export an unsigned transaction which I can sign for example with Electrum or signrawtransaction, save and re-import in Clam to broadcast. I'm looking for a method where I don't need to give Clam any access to any private key. I think there is a simpler solution.
1) Move all BTC off the addresses that had BTC on the distribution day to new addresses on your Trezor hardware wallet. 2) Import the private keys of all these addresses into the clam client 3) Get the clams [!] 4) Discard the Bitcoin private keys used to get clams and never use them again.
That way you do not have to be as careful as is described above.
I'm aware that you can first empty the BTC address to a new one, but that's not an option in some cases (like, giving up my sig address).
Not to mention that it would also imply to change all addresses in use for payouts with other services. To get some clams, I'd have to update each and every account where I have a btc address configured. That's not a solution.
|
|
|
With so many replies I might have missed the answer to the following:
Is it possible to claim clams by signing a message with your privkey?
Giving the privkey to some website, or some other software (even if it might be legit) is not a valid option. I'm aware that you can first empty the BTC address to a new one, but that's not an option in some cases (like, giving up my sig address). If signed proof isn't possible/planned, then I'll just ignore my clams to be on the safe side.
|
|
|
thats what i have ... (i need a working methode to can add this data and use the coins)
Well, I guess you will have quite a few people working on your problem already by now by posting this information. Depending on the passwords you used, someone might get lucky brute-forcing it. You can get an explanation of the format here: https://blockchain.info/de/wallet/wallet-formatMaybe you want to take a look into something like this: https://github.com/FuzzyHobbit/btc-recover
|
|
|
long string /short string A==
If the string ends with == then that looks like base64 padding. Try to treat it as a base64 string and decode that. Either pick your favorite programming language, or open the webconsole in eg Firefox (ctrl+shift+k) and type into the JS console: atob('string_goes_here')
|
|
|
You could still store the values as DECIMAL or BIGINT and benefit from sql's operations, like SUM(). At worst, you can CAST() your SELECT to CHAR when using a query in PHP. PHP has always been more like a bandaid language (like, is it ($haystack, $needle) or ($needle, $haystack) for whatever function)?
|
|
|
Whenever you are building any Bitcoin web application, you will probably have to store some Bitcoin balances, and make simple calculations to update them; and, if you already tried to do this, you will know that using traditional Integers, Big-Integrers, and Floats can cause serious problems.
That is why most developers use Strings and Character arrays.
No. Just no. I've been using decimal(16,8) for years without a single issue; and in contrast to your suggestion, it lets me do standard arithmetic operations in SQL. Same for bigint. Care to give examples for these "serious problems"? Why don't you file a bug to get those problems fixed? Let's check what MySQL says about this: The declaration syntax for a DECIMAL column is DECIMAL(M,D). The ranges of values for the arguments are as follows:
M is the maximum number of digits (the precision). It has a range of 1 to 65.
D is the number of digits to the right of the decimal point (the scale). It has a range of 0 to 30 and must be no larger than M.
The maximum value of 65 for M means that calculations on DECIMAL values are accurate up to 65 digits. This limit of 65 digits of precision also applies to exact-value numeric literals, so the maximum range of such literals differs from before.
|
|
|
That's what I came up with: <style> .adblockclass { display:block; } .adblockclass td { display:table-cell !important; min-width:0; } </style> <div class="adblockclass"> ad goes here </div>
The dodadoo ad is a bit misaligned, but the others work just fine. I tried to keep it down to a minimal. If you "margin-left:18%" the div, you could shift it.
|
|
|
Why do people still buy ripple when we know that the owners have stored with them so much ripple from the beginning?
Why do people still buy bitcoin when we know that the early adopters have stored with them so much bitcoin from the beginning?
|
|
|
im not the one who is using???
I'm talking about your example. It's bad practice and should be deprecated. Building queries like that is the reason why injections exist and are so common. addslashes shouldn't exist in PHP, nor should it's replacement mysqli_real_escape_string because it promotes bad code.
|
|
|
Brisky had fixed it for u, but i would like to suggest also : addslashes use it only on POST & GET variables, do not use it with full query for example $mypost = addslashes($_GET['id']); $sql = "SELCET * FROM `tables` WHERE `id`='.$mypost';";
It's 2017. Stop building queries like that, use prepared statements and forget all those crutches to avoid injections.
|
|
|
echo "<script type='text/javascript'>alert('Web Site Under Test -- line 440');</script>";
$tempstr = addslashes($where_sql); echo "<script type='text/javascript'>alert('$where_sql -- ".$where_sql."');</script>";
echo "<script type='text/javascript'>alert('Web Site Under Test -- line 445');</script>";
|
|
|
Just visited it for the first time too.
I wasn't using the "latest & greatest (tm)" browser, so I was greeted with nothing but a gray page and a footer (with JS enabled). That's a major failure. Any developers delivering such a product without basic HTML functionality would lose their jobs where I work.
A quick look at the used Epochtalk forum docs shows that it relies on AngularJS 1.4. What means that the board is pretty much a stillbirth already since AngularJS 2 has been released (a year ago), and there is no migration path so all AngularJS 1.x code needs to be completely rewritten for AngularJS 2.
|
|
|
If you want to check perms, here are the default ones from a CentOS7 box of mine: [root@srv ~]# rpm -q mariadb-server mariadb-server-5.5.50-1.el7_2.x86_64
[root@srv ~]# rpm -V mariadb-server
[root@srv ~]# ls -laZ /var/lib/mysql/mysql.sock srwxrwxrwx. mysql mysql system_u:object_r:mysqld_var_run_t:s0 /var/lib/mysql/mysql.sock
[root@srv ~]# ps aux | grep -v grep | grep mariadb mysql 15079 0.1 7.9 904956 80768 ? Sl 09:20 0:00 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib64/mysql/plugin --log-error=/var/log/mariadb/mariadb.log --pid-file=/var/run/mariadb/mariadb.pid --socket=/var/lib/mysql/mysql.sock
Fix perms in case they are messed up [root@srv ~]# chmod 777 /var/lib/mysql/mysql.sock [root@srv ~]# restorecon -rF /var/lib/mysql/
I don't think it might be a SELinux issue, but you can try [root@srv ~]# setsebool -P httpd_can_network_connect_db on
|
|
|
CloudFlare is no valid option for anything security related. You don't want anybody to be able to access the data between users and Bitcointalk. The standard CloudFlare SSL service requires a customer to share their site’s SSL key with CloudFlare. Keyless SSL requires that CloudFlare decrypt, inspect and re-encrypt traffic for transmission back to a customer’s origin. Source: https://www.cloudflare.com/keyless-ssl/Also, CloudFlare by default treats Tor traffic as malicious. Many users here rely on Tor. Source: https://blog.torproject.org/blog/trouble-cloudflare
|
|
|
find /var/log/ -type f -name '*.log' -delete You can run that on / too, but it might delete more than you expect. Stick to /var/log/, that's where logs should go
|
|
|
|