Topic: [ANN][ZET] Zetacoin - SHA256 - Upgrade to 0.13.2 (Segwit) - page 69. (Read 464036 times)

Quote from: Djinou94 on June 04, 2014, 06:28:45 PM

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

What FreeBSD is?

It's a UNIX OS, like Linux. To simplify it, we can say it's very similar to Linux (this definition will explain it for most people, even though it's maybe not technically correct)

Unix is like the "common root" of both Linux and FreeBSD - FreeBSD being the closer one to the "ancient" original (Unix is older than DOS/Windows)

FreeBSD has an even more liberal approach to licensing than Linux (the BSD license) that allows you to do anything with its code, even take it, modify it, and sell it (both APPLE MAC OS X and MICROSOFT WINDOWS did this, they took code from FreeBSD and used it as their own - especially MAC OS X / Darwin which is basically just FreeBSD with modifications )

FreeBSD is popular for its ports system that have been copied by Gentoo Linux and its rock-solid security

It's used a lot for servers like his cousins OpenBSD and NetBSD

The name BSD means Berkeley Software Distribution because it was created by the University of California, Berkeley

FreeBSD is more popular for servers than desktops, but you can also use it for desktop because FreeBSD WILL RUN Linux software (most Linux software works in FreeBSD using "Linux binaries")

tuaris

hero member

Activity: 780

Merit: 501

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

What FreeBSD is?

It's an operating system
http://freebsd.org

Netflix and Yahoo use it.

Djinou94

legendary

Activity: 1036

Merit: 1000

Quote from: tuaris on June 04, 2014, 02:35:22 PM

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

What FreeBSD is?

gustav

hero member

Activity: 602

Merit: 500

are there good news? what's going on with zet?

skeem

full member

Activity: 229

Merit: 100

Quote from: skeem on June 04, 2014, 02:29:34 PM

Quote from: tuaris on June 04, 2014, 02:35:22 PM

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

I believe what you are describing is the expected behavior since you are copying the entire wallet.dat file. The addresses are already "pre-generated". This is what Bitcoin refers to as the keypool: https://en.bitcoin.it/wiki/Key_pool

Though that would not explain what your seeing on Windows.
I will look into this further. Zetacoin has some quirks and this could be another.

Do you mean when the wallet.dat is generated at the first time, some addresses are "pre-generated"?

Correct. These three pages should explain how the keypool works and the purpose of it:

https://bitcointalksearch.org/topic/key-pool-feature-for-safer-wallet-backup-1414
http://bitcoin.stackexchange.com/questions/14069/key-pool-in-wallet-softwares
http://bitcoin.stackexchange.com/questions/5487/once-a-wallet-file-is-initially-created-does-the-reference-client-generate-addi

Basically it allows for safer backups.

I am sorry, I read them and want to do more test. I guess the paper wallet only has one key-pair. So I will test the paper wallet too.

skeem

full member

Activity: 229

Merit: 100

Quote from: skeem on June 04, 2014, 02:29:34 PM

Quote from: skeem on June 04, 2014, 02:29:34 PM

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

I believe what you are describing is the expected behavior since you are copying the entire wallet.dat file. The addresses are already "pre-generated". This is what Bitcoin refers to as the keypool: https://en.bitcoin.it/wiki/Key_pool

Though that would not explain what your seeing on Windows.
I will look into this further. Zetacoin has some quirks and this could be another.

Do you mean when the wallet.dat is generated at the first time, some addresses are "pre-generated"?

Correct. These three pages should explain how the keypool works and the purpose of it:

https://bitcointalksearch.org/topic/key-pool-feature-for-safer-wallet-backup-1414
http://bitcoin.stackexchange.com/questions/14069/key-pool-in-wallet-softwares
http://bitcoin.stackexchange.com/questions/5487/once-a-wallet-file-is-initially-created-does-the-reference-client-generate-addi

Basically it allows for safer backups.

But I believe I backup wallet.dat and keep it safe is safer than the key pool. Grin

tuaris

hero member

Activity: 780

Merit: 501

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

I believe what you are describing is the expected behavior since you are copying the entire wallet.dat file. The addresses are already "pre-generated". This is what Bitcoin refers to as the keypool: https://en.bitcoin.it/wiki/Key_pool

Though that would not explain what your seeing on Windows.
I will look into this further. Zetacoin has some quirks and this could be another.

Do you mean when the wallet.dat is generated at the first time, some addresses are "pre-generated"?

Correct. These three pages should explain how the keypool works and the purpose of it:

https://bitcointalksearch.org/topic/key-pool-feature-for-safer-wallet-backup-1414
http://bitcoin.stackexchange.com/questions/14069/key-pool-in-wallet-softwares
http://bitcoin.stackexchange.com/questions/5487/once-a-wallet-file-is-initially-created-does-the-reference-client-generate-addi

Basically it allows for safer backups.

skeem

full member

Activity: 229

Merit: 100

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

I believe what you are describing is the expected behavior since you are copying the entire wallet.dat file. The addresses are already "pre-generated". This is what Bitcoin refers to as the keypool: https://en.bitcoin.it/wiki/Key_pool

Though that would not explain what your seeing on Windows.
I will look into this further. Zetacoin has some quirks and this could be another.

Thank you. I got it:
$ zetacoind --help | grep key
-keypool= Set key pool size to (default: 100)
-salvagewallet Attempt to recover private keys from a corrupt wallet.dat
-rpcsslprivatekeyfile= Server private key (default: server.pem)

skeem

full member

Activity: 229

Merit: 100

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

I believe what you are describing is the expected behavior since you are copying the entire wallet.dat file. The addresses are already "pre-generated". This is what Bitcoin refers to as the keypool: https://en.bitcoin.it/wiki/Key_pool

Though that would not explain what your seeing on Windows.
I will look into this further. Zetacoin has some quirks and this could be another.

Do you mean when the wallet.dat is generated at the first time, some addresses are "pre-generated"?

Tyke

legendary

Activity: 1535

Merit: 1208

Zetacoin is in my book called Cryptocurrency "The Alt-ernative". Here is first draft of IFC:

https://bitcointalksearch.org/topic/m.7131241

Zetacoin will look similar to this. Coin specifications, history, exchanges and other miscellaneous details will be included. Please help fund the publication of this book which I plan to publish this summer.

ZaSz7txCRL2KnzZmFQT7NZkNAL33Qj4ih8

tuaris

hero member

Activity: 780

Merit: 501

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

I believe what you are describing is the expected behavior since you are copying the entire wallet.dat file. The addresses are already "pre-generated". This is what Bitcoin refers to as the keypool: https://en.bitcoin.it/wiki/Key_pool

Though that would not explain what your seeing on Windows.
I will look into this further. Zetacoin has some quirks and this could be another.

skeem

full member

Activity: 229

Merit: 100

The zetacoin android wallet is bad. It will always connect to the Internet even if I disconnect it. It eats my phone traffic without my permission. So maybe I have to identify it as spamware.

And the FreeBSD daemon has a strange problem. When I copy the wallet.dat to several different machines and run, all machines will generate an extra same address. I don't like this extra address, because I only want one address in my wallet.dat. Otherwise, why are the extra addresses the same? I guess they have been calculated by the same algorithm pattern? So maybe the source code has been hacked by bad guy?

I'm the maintainer of that port.
Can you PM me to explain what's happening? I don't understand what you mean.

1. Start the zetacoind, so it has an address: ABC.
2. zetacoind getaddressesbyaccount "" shows it has only one address: ABC
3. Then backup wallet.dat to initial-wallet.dat
4. Send some coins to ABC,
5. zetacoind getaddressesbyaccount "" shows it has only one address: ABC.
6. After a while, zetacoind getaddressesbyaccount "" shows it has another address: PDQ
7. Stop zetacoind, delete wallet.dat,
8. copy initial-wallet.dat to /var/db/zetacoin/wallet.dat
9. Start zetacoind, zetacoind getaddressesbyaccount "" shows it has one address: ABC,
10. But after finishing synchronizing data, zetacoind getaddressesbyaccount "" shows it has address: PDQ too.
11. Copy initial-wallet.dat to another computer's /var/db/zetacoin/wallet.dat, and start zetacoind, zetacoind getaddressesbyaccount "" shows it has only one address ABC, but after finishing synchronization, zetacoind getaddressesbyaccount "" shows it has the same address PDQ.
12. But when I copy initial-wallet.dat to a windows computer, it always shows only one address: ABC.

Do I meet a ghost?

tuaris

hero member

Activity: 780

Merit: 501