Bitcoin Forum
December 15, 2017, 02:35:55 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 ... 424 »
  Print  
Author Topic: [ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. "Clamcoin"  (Read 1096465 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
AllAltNews
Member
**
Offline Offline

Activity: 60

Follow @AllAltNews on Twitter and Facebook!


View Profile WWW
May 27, 2014, 05:31:32 AM
 #121

No Twitter or Facebook to help promote?

Aero - Innovation, Progression and Excellence!
Next big thing? AeroME, read the Whitepaper
1513348555
Hero Member
*
Offline Offline

Posts: 1513348555

View Profile Personal Message (Offline)

Ignore
1513348555
Reply with quote  #2

1513348555
Report to moderator
1513348555
Hero Member
*
Offline Offline

Posts: 1513348555

View Profile Personal Message (Offline)

Ignore
1513348555
Reply with quote  #2

1513348555
Report to moderator
"Governments are good at cutting off the heads of a centrally controlled networks like Napster, but pure P2P networks like Gnutella and Tor seem to be holding their own." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
mibz0r
Jr. Member
*
Offline Offline

Activity: 31


View Profile
May 27, 2014, 09:02:13 AM
 #122

From which date was the data dump? I only have one btc private key from a multibit wallet that held different amounts of btc in the recent past, but unfortunately importing it to the CLAM wallet didnt yield any CLAM, so I guess the data dump was made before I received btc on this address
How did you do this?
first make sure you understand that you shouldnt be exposing a private key to a address that still hold coins, so understand it and dtake the appropriate measures.
on multibit go tools -> export private keys
select "do not password protect" so you can read the keys in plaintext, then export it to a file, read the file in a text editor and copy the private key(s)
on CLAM go to help -> debug window -> console
importprivkey x  (where x is the private key you are importing)
restart clam and launch the wallet with the -salvagewallet argument
Didn't work for me it just keeps saying invalid key, also I don't know how to export the private key from my Android to a readable format so yet again I'm feeling like I won't get the Clams assigned to my addresses Sad

Don't lose hope, friend Smiley

A MultiBit key dump should look something like this:

# KEEP YOUR PRIVATE KEYS SAFE !
# Anyone who can read this file can spend your bitcoin.
#
# Format:
#   <Base58 encoded private key>[<whitespace>[<key createdAt>]]
#
#   The Base58 encoded private keys are the same format as
#   produced by the Satoshi client/ sipa dumpprivkey utility.
#
#   Key createdAt is in UTC format as specified by ISO 8601
#   e.g: 2011-12-31T16:42:00Z . The century, 'T' and 'Z' are mandatory
#
KwEGbfZzry1ZHbuiPgQet8tCs3Jn2GgPrmK98aia4nfELViS5yPX 2014-05-25T14:32:37Z
# End of private keys

If your dump doesn't look similar to that ^^^ Then, you likely need to click "Do not password protect" before you dump.

In that dump above, the privateKey you need to import is this string of characters:

KwEGbfZzry1ZHbuiPgQet8tCs3Jn2GgPrmK98aia4nfELViS5yPX

So the command:

importprivkey KwEGbfZzry1ZHbuiPgQet8tCs3Jn2GgPrmK98aia4nfELViS5yPX

^^ Should do the trick.



As far as the Android wallet, could you please link us directly to the Android wallet your speaking of?
So we can take a look and see if we can find any info for you?



Even if the above fails, don't give-up hope Grin

We intend to keep hammering away at this until we get it simplified and tutorialized.

Keep checking back with us!

Doesn't work, I did exactly what you said and it just says Invalid Private Key, as for the Android wallet I mean the Dogecoin wallet
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 27, 2014, 10:54:37 AM
 #123

We added a new guide to the main Post for MultiBit!

Grin Grin Grin Grin Grin



Please let us know how it works for you!

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
maardein
Sr. Member
****
Offline Offline

Activity: 420


View Profile
May 27, 2014, 10:59:22 AM
 #124

This sounds fun and interesting. However, I was wondering, is there a way to check your clam balance (or the balance you are 'entitled' to)  without importing your wallet.dat first?

BTC: 1788UegKXGXXicfPcbZ1bmSUJ99ZWRCF7p
LTC: LZ2rCcoxK4X8wRRynqdxoimd4d3TDNk7Lk
PMP: PApSSdorQds5tQysymwDXPAN3viJLFTUs8
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 27, 2014, 11:14:24 AM
 #125

This sounds fun and interesting. However, I was wondering, is there a way to check your clam balance (or the balance you are 'entitled' to)  without importing your wallet.dat first?

A complicated answer:

Yes, and No.

If you understood change addresses (which do NOT show up in the client, and most users don't even know they have them) you could take a look at the CLAMS block chain and see if those addresses have a balance.

However, to make this even more difficult, the first time you start the Bitcoin, Litecoin, or Dogecoin Client it creates no less than 100 change addresses.

However, to make this even more difficult, every single time you send coins you use up a change address, and your Client periodically creates more change addresses.

However, to make this even more difficult, the addresses in the Bitcoin, Litecoin, or Dogecoin Client would need to be converted into an address that could be searched on the CLAM Network.  This would require a hand-rolled script.

So, the short answer is, "yes."

The Long answer is, "It is quite difficult."

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
maardein
Sr. Member
****
Offline Offline

Activity: 420


View Profile
May 27, 2014, 11:20:47 AM
 #126

This sounds fun and interesting. However, I was wondering, is there a way to check your clam balance (or the balance you are 'entitled' to)  without importing your wallet.dat first?

A complicated answer:

Yes, and No.

If you understood change addresses (which do NOT show up in the client, and most users don't even know they have them) you could take a look at the CLAMS block chain and see if those addresses have a balance.

However, to make this even more difficult, the first time you start the Bitcoin, Litecoin, or Dogecoin Client it creates no less than 100 change addresses.

However, to make this even more difficult, every single time you send coins you use up a change address, and your Client periodically creates more change addresses.

However, to make this even more difficult, the addresses in the Bitcoin, Litecoin, or Dogecoin Client would need to be converted into an address that could be searched on the CLAM Network.  This would require a hand-rolled script.

So, the short answer is, "yes."

The Long answer is, "It is quite difficult."

Ok, I understand it would take a lot of time.

Another question. If I have multiple wallets (say dogecoin and litecoin), is there a way to import multiple wallet.dat files? I tried 'importwallet' but I am getting an error, probably because the wallet.dat is encrypted. Is there a way to import, without first undoing encryption of original wallet, saving unencrypted wallet.dat, and re-encrypting?

BTC: 1788UegKXGXXicfPcbZ1bmSUJ99ZWRCF7p
LTC: LZ2rCcoxK4X8wRRynqdxoimd4d3TDNk7Lk
PMP: PApSSdorQds5tQysymwDXPAN3viJLFTUs8
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 27, 2014, 12:27:15 PM
 #127

This sounds fun and interesting. However, I was wondering, is there a way to check your clam balance (or the balance you are 'entitled' to)  without importing your wallet.dat first?
A complicated answer:
Yes, and No.
If you understood change addresses (which do NOT show up in the client, and most users don't even know they have them) you could take a look at the CLAMS block chain and see if those addresses have a balance.
However, to make this even more difficult, the first time you start the Bitcoin, Litecoin, or Dogecoin Client it creates no less than 100 change addresses.
However, to make this even more difficult, every single time you send coins you use up a change address, and your Client periodically creates more change addresses.
However, to make this even more difficult, the addresses in the Bitcoin, Litecoin, or Dogecoin Client would need to be converted into an address that could be searched on the CLAM Network.  This would require a hand-rolled script.
So, the short answer is, "yes."
The Long answer is, "It is quite difficult."
Ok, I understand it would take a lot of time.
Another question. If I have multiple wallets (say dogecoin and litecoin), is there a way to import multiple wallet.dat files? I tried 'importwallet' but I am getting an error, probably because the wallet.dat is encrypted. Is there a way to import, without first undoing encryption of original wallet, saving unencrypted wallet.dat, and re-encrypting?

Sure, thanks for stopping in Grin

So, the multiple wallets is the more difficult part.

As far as encryption is concerned, we have imported an encrypted wallet, without un-encrypting it.  It is simply STILL an encrypted wallet once it is inside of the CLAM Client, i.e. you need your passphrase to dispose of your CLAMS.



The dumpwallet/importwallet command is a command created by Sipa.  The format it dumps in is NOT the same format as the wallet.dat file.

MultiBit uses the same format when you "Export" your wallet, and the core Bitcoin client uses the same format when you "dumpwallet".
To my knowledge, Litecoin and Dogecoin do NOT have the importwallet/dumpwallet command at all.



AGAIN, ALWAYS HAVE A BACK-UP IN A SAFE PLACE.

To do multiple encrypted wallets, one would have to copy the encrypted wallet.dat file over to the AppData/Clam/ folder, and run the CLAM Client with --salvagewallet.  The double -- is important.  This would have be done for each wallet.

To get all of the coins into a single wallet, the coin would have be sent to an address in a single wallet, after each was imported.



Hope that helps and makes sense!!

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
May 27, 2014, 03:23:26 PM
 #128

If you do want them, well.... then: Your Welcome Smiley

<justpedantic>
Your -> You're
</justpedantic>

<actuallyimportant>
You're apparently contradicting yourself ...

Your instructions in the OP:
Quote
9. Run the CLAM Client with the commandline argument -salvagewallet.
...
Quote
8. Run the CLAM Client from the command line adding the -salvagewallet argument.

And from a subsequent response of yours:
Quote
run the CLAM Client with --salvagewallet.  The double -- is important.
</actuallyimportant>

HTH.

Cheers,

Graham
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
May 27, 2014, 04:11:31 PM
 #129

Anybody had successfully received some CLAMs?

Yes. After reading through the instructions and subsequent confirmatory posts, I decided to take the direct route.

I have standard linux wallets for BTC, LTC and DOGE.

BTC and LTC wallets are empty, never seen any transactions so neither are due to receive CLAMs because the addresses have never been recorded in the bitcoin blockchain as part of a transaction.

But all is not lost, I am a (lapsed) Shibe and my DOGE wallet address has at some time in the past been recorded in the Dogecoin blockchain as part of a transaction (when I acquired the DOGE and when I credited the tipbot's address).

Code:
$ cat /etc/issue
Ubuntu 14.04 LTS \n \l
$ cd /tmp
$ git clone https://github.com/nochowderforyou/clams
$ cd clams
$ qmake-qt4                                              # Qt5 menubar icons and ubuntu unity don't place nice.
$ make -j4                                               # entry-level core i3 (Sandybridge) Acer laptop
                                                         # I ignored several compiler warnings about an unchecked
                                                         # return type, might hack up a PR later.
$ ./clam-qt -printtoconsole -debug
^C
$ cp ~/Documents/BackupWallets/dogecoin-unsecured-backup-wallet-00.dat ~/.clam/wallet.dat
$ ./clam-qt

Works for me, better than expected, I got 4 separate credits of 4.60545574 CLAM.

Why 4 credits, I wonder?

And it's successfully staking, a transaction just showed up in the wallet, itemised as "Mined", totalling 0.00136895.

The overview states I have 13.8-odd CLAM to spend and I am staking 4.6-odd CLAM

Quote

Status: 1/unconfirmed, broadcast through 5 nodes
Date: 27/05/2014 16:55
Source: Generated
Debit: 0.00 CLAM
Net amount: -4.60545574 CLAM
Transaction ID: 1e605b6726a3682ac739dfe8f2fa96e9479b7271d2da484a40946a9dc62a2da5

Generated coins must mature 510 blocks before they can be spent.


(I shuffled the transaction hash id before posting)

Congratulations on what's beginning to look like a solid implementation of a really well-considered approach.

Cheers,

Graham
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 28, 2014, 12:24:08 AM
 #130

If you do want them, well.... then: Your Welcome Smiley
<justpedantic>
Your -> You're
</justpedantic>
<actuallyimportant>
You're apparently contradicting yourself ...
Your instructions in the OP:
Quote
9. Run the CLAM Client with the commandline argument -salvagewallet.
...
Quote
8. Run the CLAM Client from the command line adding the -salvagewallet argument.
And from a subsequent response of yours:
Quote
run the CLAM Client with --salvagewallet.  The double -- is important.
</actuallyimportant>
HTH.
Cheers,
Graham

Thank you very much for the corrections.
Indeed, the command line mistake was a very important one!

Think the OP post should be correct now, and reflect the changes.



Anybody had successfully received some CLAMs?
Yes. After reading through the instructions and subsequent confirmatory posts, I decided to take the direct route.
I have standard linux wallets for BTC, LTC and DOGE.
BTC and LTC wallets are empty, never seen any transactions so neither are due to receive CLAMs because the addresses have never been recorded in the bitcoin blockchain as part of a transaction.
But all is not lost, I am a (lapsed) Shibe and my DOGE wallet address has at some time in the past been recorded in the Dogecoin blockchain as part of a transaction (when I acquired the DOGE and when I credited the tipbot's address).
Code:
$ cat /etc/issue
Ubuntu 14.04 LTS \n \l
$ cd /tmp
$ git clone https://github.com/nochowderforyou/clams
$ cd clams
$ qmake-qt4                                              # Qt5 menubar icons and ubuntu unity don't place nice.
$ make -j4                                               # entry-level core i3 (Sandybridge) Acer laptop
                                                         # I ignored several compiler warnings about an unchecked
                                                         # return type, might hack up a PR later.
$ ./clam-qt -printtoconsole -debug
^C
$ cp ~/Documents/BackupWallets/dogecoin-unsecured-backup-wallet-00.dat ~/.clam/wallet.dat
$ ./clam-qt
Works for me, better than expected, I got 4 separate credits of 4.60545574 CLAM.
Why 4 credits, I wonder?
And it's successfully staking, a transaction just showed up in the wallet, itemised as "Mined", totalling 0.00136895.
The overview states I have 13.8-odd CLAM to spend and I am staking 4.6-odd CLAM
Quote

Status: 1/unconfirmed, broadcast through 5 nodes
Date: 27/05/2014 16:55
Source: Generated
Debit: 0.00 CLAM
Net amount: -4.60545574 CLAM
Transaction ID: 1e605b6726a3682ac739dfe8f2fa96e9479b7271d2da484a40946a9dc62a2da5
Generated coins must mature 510 blocks before they can be spent.

(I shuffled the transaction hash id before posting)
Congratulations on what's beginning to look like a solid implementation of a really well-considered approach.
Cheers,
Graham

Super happy to hear you've had a good experience with the import process Grin

And a stake right away! 
Likely due to the fact that the coins had been accruing "coinDays"/age since the sends were done.
That effect should only get more powerful as time goes on.
New users will have a great deal of coinDays accrued and hopefully stake quite quickly on the network!

Concerning the 4 separate credits:

The block chain does not (thankfully) store information connecting multiple addresses within the same wallet.  Evidentally, there were 4 separate outputs on the DOGE block chain to 4 separate addresses in your wallet -> thus 4 separate credits!

We did our best to try to formulate rules that would be as fair as possible, alas there is only so much data on the block chain.

Like we've said previously, it isn't perfect: but it includes everyone!

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
emmnazady
Sr. Member
****
Offline Offline

Activity: 284


www.btcnews.my


View Profile WWW
May 28, 2014, 01:48:13 AM
 #131

Code:
1. Download the CLAM Client, below.
2. Find the location of your BTC, LTC, or DOGE wallet.dat file.
3. This is usually the folder: "C:/Users/<YOUR_USERNAME>/AppData/Roaming/<COIN_NAME>/"
4. You may have to enable "Show Hidden Files And Folders" to see this folder.
5. Replace <YOUR_USERNAME> with your Windows account username.
6. Replace <COIN_NAME> with either Bitcoin, Litecoin, or Dogecoin.
7. Inside of that folder you will find the WALLET.DAT file that holds the private keys for your wallet.
8. Make a copy of this file and place it in your "C:/Users/<YOUR_USERNAME>/AppData/Roaming/Clam/" folder.
9. Run the CLAM Client with the commandline argument --salvagewallet (Note the double --).
10. You should see your Clams.
   Can  someone make images tutorial for this  Cry

                                 
                  █████████████████████████████▒
               ▒███████████████████████████████▓░
             ▒████▓                         ░▓███▒░░
         ░▒▓████▓░                            ░▓███▓▓▒▒░░
▓▓▓▓▓████████▓▒               ░░░▒▒▒▒▒░         ░▒█████████▓▓▓▓▓
████████▓▒▒░              ░▒▓▓▓▒▒▒▒▒▒▒▓▓▓▓▒         ░░▒▒████████
▓██▓                   ░▒▓▓▓▒▒▒▒▒▒▒▒▒▒▒▒▒▓███▒░             ███▓
▒███                 ░▓█▓▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▓▓█████▒░         ▓▓█░
░█▓█░               ▓█▓▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▓▓▓▓▓▓█████▓██░     ▓███░
 ▓██▓             ▒██▒▒░▒▒▒▒▒▒▒░▒▒▒▒▒▒▒▒▒▒▒░▒▒░  ░▓█▓      ███▓
 ▒█▓█░           ▓█▓▒▒▒▒▒▒▒▒▒▒░▒░▒░░░░░▒▒░ ░▒░░▓███▓      ▒███▒
  █▓█▓          ▓█▓▒▓▒▒▒▒░░░░░░░░░░░░▒▓▒▒░░▒▒▓█████░      ███▓
  ▒█▓█░        ░██▓▓▒░░░░░░░░░▒▓▒░ ░░░ ░░▒▒▓▓▓▓▓█▒█░     ▓███▒
   ▓▓▓▓        ███▒░░░░░▒░░░▒▒▒▒▒░░░░░▒▒▒▒▒▒▒▒▒▓▓ █░    ▒███▒
   ░▓▓▓▓   ░▒▒ █▓▒▒▒▒▒▓▓▓▒░▒░░░░░░░▒▒▒▒▒▒▒▒▒░▒▒▓ ▒█    ░████▒
    ░▓▒▓▒ ░▓████▓▓▓▒▒▒▓▒░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒▒▒▒  ██   ░████▒
     ▒▓▓██  ▓████▓▒▒░░░░░░░░░▒▒▒▒▒▒▒▒▒▒▒░▒░▒▒░ ░██▒  ░████▒
      ▓████  ░██████▓▓▓▓▓▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒░░  ░███▓  ░████░
       ▒████   ▓█▓░█████▓▓▒▒▒▒▒▒▒▒▒▒░░░░░░▒▓████░  ▒████▒
        ░████▒  ▒░   ▒██████▓▓▓▒▒▒▒▒▒▒▓██████▓░   ▓████▒
          ████▓         ░▒▓██████████████▓░░    ░████▓
           ▒████▒                              ▓████░
             ▓████░                          ▒████▒
              ░████▓░                      ▒████▓
                ░████▓░                  ▒████▓░
                  ░████▓░              ▒████▓░
                     ░▓████▒          ▓████▒░
                       ░▒████▓░    ▒████▓▒
                          ░▓████▓▓████▓░
                             ▒█████▓░
                               ░▒▒░
✬✬✬✬✬

gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
May 28, 2014, 02:08:34 AM
 #132


Concerning the 4 separate credits:

The block chain does not (thankfully) store information connecting multiple addresses within the same wallet.  Evidentally, there were 4 separate outputs on the DOGE block chain to 4 separate addresses in your wallet -> thus 4 separate credits!

Ah, I think I get it - thanks.

Just to check my understanding, am I correct in surmising that there's a bonanza of CLAMs heading out to those people who actually followed the recommendations?

Quote
"as a common measure of security and privacy, it is ALWAYS recommended that users use a different receive address for each payment they receive."

If so, good for them.

Cheers,

Graham
phzi
Hero Member
*****
Offline Offline

Activity: 672


View Profile
May 28, 2014, 04:43:09 AM
 #133

Ah, I think I get it - thanks.

Just to check my understanding, am I correct in surmising that there's a bonanza of CLAMs heading out to those people who actually followed the recommendations?

Quote
"as a common measure of security and privacy, it is ALWAYS recommended that users use a different receive address for each payment they receive."

If so, good for them.
Yes and no.  If they left coins in those addresses, and still had them when CLAM did their blockchain dumps, then yes.  I use a unique receiving address for everything, but then bundle the coins into other addresses on occasion, so in my case I don't have coins in all the receiving addresses, and wouldn't get CLAMs for those (but I would get 4clam for each "bundle" address that still has coins).
zjz_lgd
Full Member
***
Offline Offline

Activity: 173

zjz_lgd


View Profile
May 28, 2014, 05:12:18 AM
 #134

Interesting.
I'd like to join in!
all the Btc address will receive coins?
I'll have a try! Roll Eyes

ShareCoin Free and Fair Distribution, Share to moon! SbuXjdoiErjmAoGd3s4jcyEWiRifuorVv3
gjhiggins
Legendary
*
Offline Offline

Activity: 1218



View Profile WWW
May 28, 2014, 06:33:42 AM
 #135

If they left coins in those addresses

<fx>sound of penny dropping</fx>

Thanks.

Cheers,

Graham
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 28, 2014, 08:02:44 AM
 #136

Code:
1. Download the CLAM Client, below.
2. Find the location of your BTC, LTC, or DOGE wallet.dat file.
3. This is usually the folder: "C:/Users/<YOUR_USERNAME>/AppData/Roaming/<COIN_NAME>/"
4. You may have to enable "Show Hidden Files And Folders" to see this folder.
5. Replace <YOUR_USERNAME> with your Windows account username.
6. Replace <COIN_NAME> with either Bitcoin, Litecoin, or Dogecoin.
7. Inside of that folder you will find the WALLET.DAT file that holds the private keys for your wallet.
8. Make a copy of this file and place it in your "C:/Users/<YOUR_USERNAME>/AppData/Roaming/Clam/" folder.
9. Run the CLAM Client with the commandline argument --salvagewallet (Note the double --).
10. You should see your Clams.
   Can  someone make images tutorial for this  Cry

That is definitely toward the top of our list "to-do" Grin



Ah, I think I get it - thanks.
Just to check my understanding, am I correct in surmising that there's a bonanza of CLAMs heading out to those people who actually followed the recommendations?
Quote
"as a common measure of security and privacy, it is ALWAYS recommended that users use a different receive address for each payment they receive."
If so, good for them.
Yes and no.  If they left coins in those addresses, and still had them when CLAM did their blockchain dumps, then yes.  I use a unique receiving address for everything, but then bundle the coins into other addresses on occasion, so in my case I don't have coins in all the receiving addresses, and wouldn't get CLAMs for those (but I would get 4clam for each "bundle" address that still has coins).

I think that sounds pretty accurate phzi.  Those who use unique receive addresses, as recommended for basic privacy, are likely to get more CLAMS - unless they gather those outputs like you've mentioned, or send funds out, which gathers them in the background.

The good news is; the basic Client tends to attempt to make sends that are "small" and include less individual outputs. 
This is because the "larger" a transaction is the more it costs in transaction fees to send.

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
coin-table
Full Member
***
Offline Offline

Activity: 224


View Profile
May 28, 2014, 09:33:16 AM
 #137


Hi,

I'm running the site www.crypto-coins-table.com

- 646 coins indexed so far (28th May 2014)
- providing detailed charts on pricing and volume
- capitalisation listing
- top and flop coins
- many filters to analyse

personalized features
- create individual watchlists
- track your coins value and compare

I have listed your coin already. To provide the full information
on your coin for all users, please use the update function.


thanks

contact us, if you would like to support or advertise on crypto-coins-table.com


All crypto coins in one table. Compare price, volume and charts - http://crypto-coins-table.com
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 28, 2014, 03:31:47 PM
 #138

Interesting.
I'd like to join in!
all the Btc address will receive coins?
I'll have a try! Roll Eyes

Indeed Smiley  All BTC addresses with a balance received CLAMS Grin

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
aKIA
Member
**
Offline Offline

Activity: 65


View Profile
May 28, 2014, 03:46:14 PM
 #139

Interresting, but should wait for the MAC OSX client Cry
SuperClam
Hero Member
*****
Offline Offline

Activity: 785


CLAM Developer


View Profile WWW
May 29, 2014, 03:02:42 AM
 #140

Interresting, but should wait for the MAC OSX client Cry

Have no fear, the OSX Client will be here very soon  Wink

https://bitcointalk.org/index.php?topic=623147
Proof-Of-Chain, 100% Distributed BEFORE Launch.
Everyone who owned BTC, LTC, or DOGE at launch got free CLAMS.
Pages: « 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 ... 424 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!