|
"diff": 182.0, This one is taking it's sweet time been a while since we had a big diff number!
Keep hashing everyone!
|
|
|
|
About time we brought back all the OP_codes.. Still don't believe this message was from Satoshi... I think people here know more than they be letting on about the removal of some of the codes. Something to hide lads? +++ b/backends/bitcoind/deserialize.py
@@ -280,10 +280,8 @@ opcodes = Enumeration("Opcodes", [
"OP_WITHIN", "OP_RIPEMD160", "OP_SHA1", "OP_SHA256", "OP_HASH160",
"OP_HASH256", "OP_CODESEPARATOR", "OP_CHECKSIG", "OP_CHECKSIGVERIFY", "OP_CHECKMULTISIG",
"OP_CHECKMULTISIGVERIFY",
- ("OP_SINGLEBYTE_END", 0xF0),
- ("OP_DOUBLEBYTE_BEGIN", 0xF000),
"OP_PUBKEY", "OP_PUBKEYHASH",
- ("OP_INVALIDOPCODE", 0xFFFF),
+ ("OP_INVALIDOPCODE", 0xFF),
])
OP_IF OP_INVALIDOPCODE 4effffffff 46726f6d2061336136316665663433333039623966623233323235646637393130623033616663353436356239204d6f6e205365702031372030303a30303a303020323030310a46726f6d3a205361746f736869204e616b616d6f746f203c7361746f7368696e40676d782e636f6d3e0a446174653a204d6f6e2c2031322041756720323031332030323a32383a3032202d303230300a5375626a6563743a205b50415443485d2052656d6f7665202853494e474c457c444f55424c4529425954450a0a492072656d6f76656420746869732066726f6d20426974636f696e20696e20663165316662346264656638373863386663313536346661343138643434653735343161376538330a696e2053657074203720323031302c20616c6d6f73742074687265652079656172732061676f2e204265207761726e6564207468617420492068617665206e6f740a61637475616c6c792074657374656420746869732070617463682e0a2d2d2d0a206261636b656e64732f626974636f696e642f646573657269616c697a652e7079207c2020202038202b2d2d2d2d2d2d2d0a20312066696c65206368616e6765642c203120696e73657274696f6e282b292c20372064656c6574696f6e73282d290a0a64696666202d2d67697420612f6261636b656e64732f626974636f696e642f646573657269616c697a652e707920622f6261636b656e64732f626974636f696e642f646573657269616c697a652e70790a696e64657820363632303538332e2e38396239623162203130303634340a2d2d2d20612f6261636b656e64732f626974636f696e642f646573657269616c697a652e70790a2b2b2b20622f6261636b656e64732f626974636f696e642f646573657269616c697a652e70790a4040202d3238302c3130202b3238302c38204040206f70636f646573203d20456e756d65726174696f6e28224f70636f646573222c205b0a2020202020224f505f57495448494e222c20224f505f524950454d44313630222c20224f505f53484131222c20224f505f534841323536222c20224f505f48415348313630222c0a2020202020224f505f48415348323536222c20224f505f434f4445534550415241544f52222c20224f505f434845434b534947222c20224f505f434845434b534947564552494659222c20224f505f434845434b4d554c5449534947222c0a2020202020224f505f434845434b4d554c5449534947564552494659222c0a2d2020202028224f505f53494e474c45425954455f454e44222c2030784630292c0a2d2020202028224f505f444f55424c45425954455f424547494e222c20307846303030292c0a2020202020224f505f5055424b4559222c20224f505f5055424b455948415348222c0a2d2020202028224f505f494e56414c49444f50434f4445222c20307846464646292c0a2b2020202028224f505f494e56414c49444f50434f4445222c2030784646292c0a205d290a200a200a4040202d3239332c3130202b3239312c3620404020646566207363726970745f4765744f70286279746573293a0a202020202020202020766368203d204e6f6e650a2020202020202020206f70636f6465203d206f72642862797465735b695d290a20202020202020202069202b3d20310a2d20202020202020206966206f70636f6465203e3d206f70636f6465732e4f505f53494e474c45425954455f454e4420616e642069203c206c656e286279746573293a0a2d2020202020202020202020206f70636f6465203c3c3d20380a2d2020202020202020202020206f70636f6465207c3d206f72642862797465735b695d290a2d20202020202020202020202069202b3d20310a200a2020202020202020206966206f70636f6465203c3d206f70636f6465732e4f505f5055534844415441343a0a202020202020202020202020206e53697a65203d206f70636f64650a2d2d200a312e372e392e340a0a OP_ENDIF
|
|
|
|
|
Works well in LTC as proof of concept.
I don't see why Bitcoin could not add MWEB and give users privacy tools.
One of the reason is probably the mixers and coinjoin services would lose there income as people stopped using them.
This is more of a reason you would not see it added.
|
|
|
|
|
{"hashrate1m": "2.1E"}
{"diff": 118.0,}
Someone pushing hard. I think block hits before 120.
|
|
|
|
Bloody hell!
AFAIK all 4 have been from the same person. Wonder what their rental cost them for this?
I don't think this is a rental. My guess is it's a large mining entity - probably swan mining - that is testing the feasibility of mining solo with their massive hashrate. If it's swan, then they have 7.5EH under their belts (and have said they are scaling to double this.) I will say it again I don't see any reason you should not fire the normal pool up again. I'm sure hashrate would land on it now with everything going on. Spoke about it before but maybe there would be scope for it again now? Pool is on fire!! Great to see the blocks flowing! Keep lucky everyone <3 |
|
|
|
I would assume fees would take over and big farms may vanish. I always wondered if bitcoin will come back to the home miners in future. Never say never!  |
|
|
|
Well done to the lucky miner.  Tick tock next block. |
|
|
|
While Bitcoin's pseudonymous nature offers a level of privacy, all transactions are public on the blockchain, allowing for potential analysis that could link identities to transactions. To enhance privacy and security, advanced cryptographic techniques such as homomorphic encryption can be applied. using Microsoft SEAL, a C++ library for homomorphic encryption, to demonstrate how privacy could be further protected in Bitcoin transactions, particularly in privacy-focused protocols like CoinJoin. Homomorphic encryption allows computations on encrypted data without needing to decrypt it first. This property can be particularly useful in Bitcoin transactions for various reasons... Users can participate in transactions without revealing their transaction amounts or other sensitive data to other parties or the public blockchain. Secure Multi-party Computations, enables the creation of complex multi-party protocols where inputs are kept private. Setting up Encryption Each participant uses a common encryption scheme set up using Microsoft SEAL. This ensures all parties can operate on the data homomorphically. users encrypt their UTXO values. This encryption does not reveal the amount of bitcoins each user intends to mix, but allows operations to be performed on the encrypted values. Ciphertext encrypted_utxo = encrypt_utxo_amount(context, utxo_amount, public_key, encryptor); Serialize and Share Encrypted UTXOs, Once encrypted, UTXO data can be serialized and securely shared with other participants or a coordinating server without revealing the actual values. string serialized_utxo = serialize_encrypted_utxo(encrypted_utxo); Aggregate Encrypted UTXOs, A trusted coordinator or the participants themselves can aggregate the encrypted UTXOs. This aggregation is performed homomorphically, ensuring that no individual inputs are exposed. Ciphertext aggregated_utxos = aggregate_utxos({encrypted_utxo1, encrypted_utxo2}, evaluator);Check Aggregated UTXOs Against Threshold: To ensure the transaction meets certain criteria (e.g., minimum input threshold for a CoinJoin), a homomorphic operation checks if the aggregated encrypted value meets the required threshold. bool meets_threshold = check_threshold(context, aggregated_utxos, threshold, decryptor, encoder); Finalize Transaction: If the check passes, the transaction can proceed. This step would typically require converting the homomorphically encrypted data into a format suitable for a Bitcoin transaction, which may involve securely decrypting the data under strict protocols or through a zero-knowledge proof mechanism to maintain confidentiality. #include <iostream>
#include "seal/seal.h"
using namespace std;
using namespace seal;
// setup the encryption context
shared_ptr<SEALContext> setup_context() {
EncryptionParameters parms(scheme_type::ckks);
size_t poly_modulus_degree = 8192;
parms.set_poly_modulus_degree(poly_modulus_degree);
parms.set_coeff_modulus(CoeffModulus::Create(poly_modulus_degree, { 60, 40, 40, 60 }));
auto context = SEALContext::Create(parms);
return context;
}
// encrypt a UTXO amount
Ciphertext encrypt_utxo_amount(shared_ptr<SEALContext> context, double amount, PublicKey public_key, Encryptor& encryptor) {
CKKSEncoder encoder(context);
Plaintext plain;
double scale = pow(2.0, 40);
vector<double> input{ amount };
encoder.encode(input, scale, plain);
Ciphertext encrypted;
encryptor.encrypt(plain, encrypted);
return encrypted;
}
// serialize a ciphertext (for sharing or storage)
string serialize_encrypted_utxo(const Ciphertext& encrypted) {
stringstream ss;
encrypted.save(ss);
return ss.str();
}
// deserialize a ciphertext
Ciphertext deserialize_encrypted_utxo(shared_ptr<SEALContext> context, const string& data) {
stringstream ss(data);
Ciphertext encrypted(context);
encrypted.load(context, ss);
return encrypted;
}
// aggregate encrypted UTXOs
Ciphertext aggregate_utxos(const vector<Ciphertext>& utxos, Evaluator& evaluator) {
Ciphertext aggregated = utxos[0];
for (size_t i = 1; i < utxos.size(); ++i) {
evaluator.add_inplace(aggregated, utxos[i]);
}
return aggregated;
}
// check if aggregated UTXOs meet the threshold
bool check_threshold(shared_ptr<SEALContext> context, const Ciphertext& aggregated, double threshold, Decryptor& decryptor, CKKSEncoder& encoder) {
// Subtract the threshold homomorphically
Plaintext plain_threshold;
encoder.encode(vector<double>{threshold}, aggregated.scale(), plain_threshold);
Ciphertext encrypted_threshold;
Encryptor encryptor(context, decryptor.public_key());
encryptor.encrypt(plain_threshold, encrypted_threshold);
Ciphertext result;
Evaluator evaluator(context);
evaluator.sub(aggregated, encrypted_threshold, result);
// Decrypt
Plaintext result_plain;
decryptor.decrypt(result, result_plain);
vector<double> result_vector;
encoder.decode(result_plain, result_vector);
return result_vector[0] >= 0;
}
int main() {
auto context = setup_context();
KeyGenerator keygen(context);
PublicKey public_key = keygen.public_key();
SecretKey secret_key = keygen.secret_key();
Encryptor encryptor(context, public_key);
Decryptor decryptor(context, secret_key);
CKKSEncoder encoder(context);
Ciphertext encrypted_utxo1 = encrypt_utxo_amount(context, 2.5, public_key, encryptor);
Ciphertext encrypted_utxo2 = encrypt_utxo_amount(context, 1.7, public_key, encryptor);
vector<Ciphertext> utxos{ encrypted_utxo1, encrypted_utxo2 };
Ciphertext aggregated = aggregate_utxos(utxos, Evaluator(context));
bool meets_threshold = check_threshold(context, aggregated, 4.0, decryptor, encoder);
cout << "Aggregated UTXOs meet threshold: " << (meets_threshold ? "true" : "false") << endl;
return 0;
}
While it's not 100% solid idea yet could be worth exploring further. |
|
|
|
They work perfect for solo hunting low power, low noise. Also opensource. Just make sure you buy one from a reputable seller. On average running higher freq and voltage I see sometimes 650gh/s or more but you should add some extra cooling if you turn it up. For the money they are great boards. Well worth getting one! https://www.thesolomining.co/ |
|
|
|
Someone been pushing hard last few days saw 1.2EH at one point again! Love the new Cpool dash top work VKBIT. Currently sitting in 9th place! "hashrate1m": "1.66T",
"hashrate5m": "1.44T",
"hashrate1hr": "775G",
"hashrate1d": "1.36T",
"hashrate7d": "52.8T",
"lastshare": 1715520194,
"workers": 3,
"shares": 285395379989,
"bestshare": 7324515159.143055,
"bestever": 268266973098,  |
|
|
|
|
Sooner everyone jumping on this bandwagon get rekt the better.
Doing nothing for Bitcoin users in the long run other than costing them money.
When someone can't send funds or make transactions because of spam junk crap we have a problem.
|
|
|
|
If you want to join the solo race I advise buying a BitAxe stand alone miner. This will get you hashing away don't burn out your GPU on your machine trying while you CAN still hash the odds of a find on a GPU or PC today are astronomical. You can get a Bitaxe from https://www.thesolomining.co/ and the main developer is active on the forum. Buy the miner, point it at the solo pool https://solo.ckpool.org And hope for a big share! Good luck! |
|
|
|
I think something like a decentralized network where users could engage in privacy-enhancing transactions without the risk of running afoul of regulatory bodies is needed. Given the situations with Samourai and Whirlpool and the scrutiny it faced it's crucial to brainstorm a structure that avoids being labeled as a money transmitter The first challenge is managing the pool of UTXOs that users wish to mix. Instead of a central server holding this info (which could draw legal and security concerns)why not let the users themselves manage their UTXOs in a peer-to-peer manner? Distributed Hash Table? Utilize a DHT to store and retrieve UTXO information, each UTXO can be indexed by a hash derived from its attributeswhich could include the transaction ID and output index, masked with a privacy-preserving algorithm to prevent tracking Adding a gossip protocol to propagate UTXO information across the network. This ensures redundancy and availability of UTXO data without relying on a central server. It would also be possible to use cryptographic commitment schemes to ensure that UTXO data remains confidential until participants are ready to reveal them. This can prevent premature exposure of UTXO details. Apply homomorphic encryption to allow certain computations to be carried out on UTXOs, such as verification of amounts and eligibility, without revealing the underlying values. Multi-Party Computation could be used for constructing the transaction where each participant computes a part of the transaction without revealing their inputs to others. This can be crucial for maintaining the confidentiality of which inputs and outputs belong to whom. Just some ideas |
|
|
|
Well done lucky miner!
"hashrate1m": "627G",
"hashrate5m": "545G",
"hashrate1hr": "502G",
"hashrate1d": "485G",
"hashrate7d": "30.9T",
"lastshare": 1714905107,
"shares": 56081400146,
"bestshare": 7324515159.143055,
"bestever": 132739990391
There was me getting excited at a 7.32G best share on the bitaxe too. |
|
|
|
Well done lucky miner! Now come on little bitaxe.. wen block. "workers": 4,
"shares": 284999958384,
"bestshare": 3219734.943005498,
"bestever": 268266973098,
|
|
|
|
Good luck to you Willi and to the whole group!
I wish you guys find a block (or two)!
Would be great if you have at least one before the halving..
thanks, but unfortunately over and no block found Unlucky guys that was some best share too! |
|
|
|
Well my small private 10ph double runs is over. Back to just the old bitaxe boards.  Wishing the 1000ph run luck smash it guys!  "hashrate1m": "1.32T",
"hashrate5m": "1.72T",
"hashrate1hr": "70.9T",
"hashrate1d": "1.36P",
"hashrate7d": "1.01P",
"lastshare": 1713391241,
"workers": 3,
"shares": 223749457214,
"bestshare": 268266973098.5093,
"bestever": 268266973098,
"authorised": 1710841905,
|
|
|
|
|
Show Posts
