Any one has got an idea of the current wealth distribution of Monero. Obviously there's no richlist but maybe someone can weigh in on the current distribution.
What qualifies as a whale? How many people do you estimate holds at least 1 XMR?
Whale = 100k+ Definitely no more than about 18M Anyone here a whale? What's your predictions on the current trends. Is it like what previous posters said, that now is accumulation time then when the current shitcoin pump fades, you will transfer wealth to XMR? |
|
|
|
|
Any one has got an idea of the current wealth distribution of Monero. Obviously there's no richlist but maybe someone can weigh in on the current distribution.
What qualifies as a whale? How many people do you estimate holds at least 1 XMR?
|
|
|
|
|
Looks like the Rise of the Premines out there. There are now more premined coins in the top 20 than ones fairly distributed such as Monero.
|
|
|
|
|
The law of 5x. Can it continue?
That seems extreme, not in cryptoland but especially true for Monero, since it rarely rises violently (except when 5x does prove true)
|
|
|
|
|
Why is price still holding so well? Usually when BTC declines, Monero goes in the dumps.
|
|
|
|
|
Predictions for January 31? Christmas has come and almost gone, price not as high as previously speculated but still quite respectable.
|
|
|
|
|
Back in the Top 10 again.
|
|
|
|
|
As long as it holds at $425 on Christmas, the Prediction Masters here are still on point.
|
|
|
|
|
What's the timeline to $500?
Need some insight from the experts here.
|
|
|
|
|
Monero is out of the top 10 again.
Will it regain strength again soon?
|
|
|
|
|
Digital Trash is pushing above $1000 and Monero is still stuck at around the $345-ish mark. What's the chance of $425 by Dec 25? Still got 8 days left.
|
|
|
|
Maybe you can do a "read" and a "write" section. So for those just looking at the balance, they can be in the read portion, sharing a blockchain. But for those wanting to make a transaction, they enter a queue to use a dedicated blockchain and get moved off after the transaction.
Daemon doesn't differentiate between reading and writing - it locks blockchain for its use in entirety. Damn, too bad. Well, good luck on the project. |
|
|
|
Can each client share the blockchain of the daemon?
Looks like they can't - I researched from original bitcoin talk and found out that sharing bitcoin directory can corrupt blockchain. So at cost of ~30GB I can support 100 concurrent users as of now. After timeout, or user leaves the site I delete his wallet(which was previously encrypted). Maybe you can do a "read" and a "write" section. So for those just looking at the balance, they can be in the read portion, sharing a blockchain. But for those wanting to make a transaction, they enter a queue to use a dedicated blockchain and get moved off after the transaction. |
|
|
|
Well, I'm stuck now with web wallet
Will community accept one-wallet web storage? I don't consider it secure, because all encryption keys are in my hands.
Multi wallet solution has reached a wall because it requires separate blockchain every time , so ~330MB per user. It does not look reasonable to handle 100 concurrent users for a cost of 32GB of storage, is it? In all other aspects it's fine - each wallet is stored securely with its own encryption key, which I don't know, and after user is done, entire wallet is deleted - it is responsibility of a user to store his private keys in a secure place.
Ideas?
EDIT: Multi blockchain solution seems reasonable only if I introduce service fees, which is not very good.
Hey nice to see a Rubyist here. I'm just a beginner so I can't help much. But don't think that's the optimal solution to have separate blockchain for each user. Can each client share the blockchain of the daemon? The other extreme solution is to translate the client code into native Ruby, but that would be a massive undertaking. |
|
|
|
Question regarding hash functions: In the mininero implementation, there is a reference to a , now is this equivalent to the reference Monero in the source? Also, this is SHA512 not SHA3-512 right, which is different. It is not equivalent, no. It seems to only be in the oldMiniNero.py file as well. SHA512 is the default for EdDSA, which Monero's crypto is based on (using Keccak for the hashing algorithm instead). So the "Hash_to_Scalar" function should use Keccak instead and not SHA512? |
|
|
|
Question regarding hash functions: In the mininero implementation, there is a reference to a , now is this equivalent to the reference Monero in the source? Also, this is SHA512 not SHA3-512 right, which is different. |
|
|
|
Help with explaining how this work?
How to create the checksum index from a list of words; can explain it in non c++ terms?
It takes the first N characters of each seed word interpreted using the UTF8 encoding (N=unique prefix length), combines them into one string, computes the crc_32 of the resulting string interpreted as a byte array, and then modulo (remainder) with the word list length. Can you explain further how the UTF8 encoding combines those first N characters into a string. Is there a specific way it does that? is a way to represent characters that sometimes uses more than one byte per character. This code takes (up to) the first N characters regardless of how many bytes each character uses. Once those characters are pulled from the words they are combined using string concatenation into a single large string which is then used as a byte array to calculate a CRC32 checksum Ok, great. I just didn't know it was a simple string concatenation after the encoding. |
|
|
|
Help with explaining how this work?
How to create the checksum index from a list of words; can explain it in non c++ terms?
It takes the first N characters of each seed word interpreted using the UTF8 encoding (N=unique prefix length), combines them into one string, computes the crc_32 of the resulting string interpreted as a byte array, and then modulo (remainder) with the word list length. Can you explain further how the UTF8 encoding combines those first N characters into a string. Is there a specific way it does that? |
|
|
|
Help with explaining how this work? How to create the checksum index from a list of words; can explain it in non c++ terms? /*!
* \brief Creates a checksum index in the word list array on the list of words.
* \param word_list Vector of words
* \param unique_prefix_length the prefix length of each word to use for checksum
* \return Checksum index
*/
uint32_t create_checksum_index(const std::vector<std::string> &word_list,
uint32_t unique_prefix_length)
{
std::string trimmed_words = "";
for (std::vector<std::string>::const_iterator it = word_list.begin(); it != word_list.end(); it++)
{
if (it->length() > unique_prefix_length)
{
trimmed_words += Language::utf8prefix(*it, unique_prefix_length);
}
else
{
trimmed_words += *it;
}
}
boost::crc_32_type result;
result.process_bytes(trimmed_words.data(), trimmed_words.length());
return result.checksum() % crypto::ElectrumWords::seed_length;
} Also, is it implementable without use of pointers and c++ specific functions such as
inline std::string utf8prefix(const std::string &s, size_t count)
{
std::string prefix = "";
const char *ptr = s.c_str();
while (count-- && *ptr)
{
prefix += *ptr++;
while (((*ptr) & 0xc0) == 0x80)
prefix += *ptr++;
}
return prefix;
}
or boost::crc_32_type result;
result.process_bytes(trimmed_words.data(), trimmed_words.length());
|
|
|
|
Can someone explain how to decrypt the .keys file?
Specifically, the load_keys function within the wallet2.cpp in the source. Can explain the logic behind it and the procedure. (Not that fluent in C)
void wallet2::load_keys(const std::string& keys_file_name, const std::string& password)
{
wallet2::keys_file_data keys_file_data;
std::string buf;
1 bool r = epee::file_io_utils::load_file_to_string(keys_file_name, buf);
THROW_WALLET_EXCEPTION_IF(!r, error::file_read_error, keys_file_name);
// Decrypt the contents
2 r = ::serialization::parse_binary(buf, keys_file_data);
THROW_WALLET_EXCEPTION_IF(!r, error::wallet_internal_error, "internal error: failed to deserialize \"" + keys_file_name + '\"');
crypto::chacha8_key key;
3 crypto::generate_chacha8_key(password, key);
std::string account_data;
account_data.resize(keys_file_data.account_data.size());
4 crypto::chacha8(keys_file_data.account_data.data(), keys_file_data.account_data.size(), key, keys_file_data.iv, &account_data[0]);
.....
I labeled some lines of the code above: 1. Loads the data file into a memory buffer 2. Parses the memory buffer into a data object 3. Derives a chacha8 decryption key from the password (this uses the CryptoNight slow hash for key stretching, which greatly limits the possibility of brute forcing). 4. Decrypts the data using the decryption key The unlabeled lines in the code are error checking, memory management, etc. Ok, that clears some things up. But what do you mean by 2. "Parse the memory buffer into a data object"? I can read the .keys file in and store it as a string but how do I do the 2nd step of parsing? What type of characters is it stored as? |
|
|
|
|
Show Posts
