Bitcoin Forum
May 09, 2024, 03:38:32 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 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 [58] 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 ... 154 »
1141  Other / Archival / Re: WasabiWallet.io | Open-source, non-custodial Bitcoin Wallet for desktop on: March 17, 2023, 01:20:43 PM
In light of chipmixer aftermath, I found interesting tweets posted recently by @btcdragonlord, who is writing articles on BitcoinMagazine.
This is his own opinion, but he explained what happened with Wasabi in last few years, and he is talking about other alternatives for Bitcoin privacy.
What stick with me was last thing he said, and I tend to agree with this... we might be little too late already, but we still have decentralized JoinMarket and I hope more people work on that, making it easier to use for regular people.
Quote
Privacy as we can see is constantly now under attack from all fronts, even within our space. But developers are not a plenty and it is not likely we going to see more projects coming around to start developing privacy solutions for us. It might be little too late already.
https://twitter.com/btcdragonlord/status/1635521127748362240

IMO this story should be shared by zkSNACKs much sooner. Even so, it's still a shame they decide to choose blacklist feature rather than either,
1. Shut down their service and list community coordinator on their wallet.
2. Stop taking profit and use different means of income (e.g. donation).
1142  Bitcoin / Development & Technical Discussion / Re: Had enough of ordinals? on: March 17, 2023, 12:23:56 PM
--snip--
Is it possible to detect which nodes have applied this patch because I think if every node did it we could remove ordinals and the problems they bring to the Blockchain?

Theoretically it's possible, but who knows how reliable is it. You can initiate connection with any full node, then send "mempool" message[1] which ask list of unconfirmed transaction. After you obtain the list, you just need to check whether it contains any Ordinals TX. Or just ask Ordinal TX data using "getdata" message[2].

[1] https://developer.bitcoin.org/reference/p2p_networking.html#mempool
[2] https://developer.bitcoin.org/reference/p2p_networking.html#getdata
1143  Bitcoin / Bitcoin Technical Support / Re: How do timelocked transactions work? on: March 17, 2023, 12:00:57 PM
By Mistake? Yes, I was trying to create a two-factor authentication wallet willingly because I thought it would be more secure. The error says: Could Not Retrieve Terms of service: ErrorConnectingServer(TimeoutError())
There are some small security benefits to using a 2FA wallet, but it comes with an additional cost in fees (both larger transaction fees and fees to the third party TrustedCoin)

For reference, the cost is 0.005BTC (for 20 outgoing TX) and 0.00125BTC (for 100 outgoing TX)[1]. And for 5-8 years, you need to consider whether TrustedCoin still rnu their service in the future.

as well as a loss of privacy due to the reliance on said third party.

Additionally, their privacy policy state their company is U.S. based and use some third party[2].

[1] https://trustedcoin.com/#/faq
[2] https://trustedcoin.com/#/privacy
1144  Bitcoin / Development & Technical Discussion / Re: Had enough of ordinals? on: March 16, 2023, 10:22:56 AM
Question: is there anyone out there that can illustrate how to remove ordinals
transactions from the mempool of my node?

Only for mempool? Use this patch and compile Bitcoin Core from source code, https://gist.github.com/luke-jr/4c022839584020444915c84bdd825831. You just need to follow compilation guide from https://github.com/bitcoin/bitcoin/tree/master/doc#building. But if you don't want to store any Ordinal data on blocks, you should run Bitcoin Core 0.12.1 or other client which doesn't support SegWit which means your node doesn't store any witness data.
1145  Bitcoin / Development & Technical Discussion / Re: Decipher xprv or seed from keystore when I know the password on: March 15, 2023, 12:31:04 PM
--snip--
Both xprv and seed are in hex. I've already told you.
I need xprv and seed to be converted to xprv in base58 format, seed to words.
--snip--

At least from seed (in hex format) to words it should be straightforward. An example,

Code:
>>> from mnemonic import Mnemonic
>>> mnemo = Mnemonic("english")
>>> xprv = '419ff3b824753f296223325a300a694a9641135558eedda79d9cb74f046e1457'
>>> len(xprv)
64
>>> xprv_bytes = bytes.fromhex(xprv)
>>> len(xprv_bytes)
32
>>> mnemo.to_mnemonic(xprv_bytes)
'dose zebra unlock employ fault net mass green focus leopard olympic news goat meadow fever build tank diagram grunt hub utility damage eyebrow view'

Take note it require library from https://github.com/trezor/python-mnemonic. And in case i also misunderstood what you want to achieve, i would suggest you to add expected input/output with some examples to your question.
1146  Bitcoin / Bitcoin Technical Support / Re: Trying to run Coinbase multisig-tool locally on Linux on: March 14, 2023, 12:27:56 PM
And Ubuntu makes it particularly hard to install Python 2 in recent versions of the distro, so you should start with an older Ubuntu version such as Trusty (14.04) or Precise (12.04) that have Python 2.7 bundled.

Not only Ubuntu, but most newer version of linux distro. And i'd recommend to use Debian 11 since it's newest version of Debian and still ship Python 2.7[1] rather than using EOL version of Ubuntu.

[1] https://packages.debian.org/bullseye/python2.7
1147  Bitcoin / Development & Technical Discussion / Re: My consternation regarding the monitoring of Bitcoin transactions. on: March 13, 2023, 12:53:27 PM
I asked other cryptocurrency users if bitcoin transactions could be tracked. Some of them say yes, but they don't explain how it can be tracked, and from what I read, all unconfirmed bitcoin transactions are sent to the mem-pool before the miners take it and mine it, then it is confirmed and added to the blockchain, so how do we know where and how bitcoin transactions can be tracked?

You might want to read basic explanation from Chainalysis at https://blog.chainalysis.com/reports/is-bitcoin-traceable/. Obviously everyone have different way to track Bitcoin.

What is the distinction between Dash and monero?

Dash is a cash grab by Evan Duffield, amplifying his insta-mine through rent-seeking masternodes.
Dash doesn't offer much in the way of privacy.
Monero on the other hand does, by hiding amounts and addresses, and by almost completely obscuring the transaction graph.

In addition, CoinJoin feature also exist on some Bitcoin wallet such as Sparrow and Samourai wallet.
1148  Bitcoin / Bitcoin Technical Support / Re: Bitcoin block size on: March 13, 2023, 12:22:59 PM
Completely your opinion. Price is high enough apparently; difficulty is in ATHs lots of months now. Also, running a node is cheap enough.
With U.S. Treasury Department Planning 30% increase in Tax on Crypto Mining Firms, will this not affect the cost of a node?  [NEWS] Biden budget proposes 30% tax on crypto mining electricity usage

1. You can run full node without perform any mining.
2. For mining pool, cost of running few nodes is negligible compared with cost of running other infrastructure or pay their worker.
3. Miner who perform mining by connecting to centralized pool don't need to run full node.
1149  Bitcoin / Bitcoin Technical Support / Re: How to be notified about the status of the mempool on: March 13, 2023, 12:05:51 PM
the mempool size they show is 33.06 MB and Johoe page shows 167 vMB.
For what it's worth: my Bitcoin Core shows 278 MB. Update: my other Bitcoin Core shows 249 MB.
I noticed Electrum has a hard time predicting the Target distance from the tip too (this started with the mempool spam).
I can't tell you why there's such a difference.

If you obtain number "278 MB" and "249 MB" from column "Memory usage", then you're comparing 2 different things. "Memory usage" refer to RAM usage to store deserialized unconfirmed TX while some website simply show total size of all unconfirmed transaction.

For other user, you can visit https://www.statoshi.info/d/000000020/memory-pool?orgId=1 to know the difference. Pay attention to chart "Mempool Transactions" and "Mempool Dynamic Memory Usage".
1150  Bitcoin / Bitcoin Discussion / Re: On Ordinals: Where do you stand? on: March 13, 2023, 10:16:31 AM
--snip--

The spam problem has its roots in two aspects:

1) the perceived low cost of the Bitcoin blockchain with respect to Ethereum,
2) the condition of Bitcoin as the "OG" cryptocurrency.

Problem 2 cannot be solved, it's even one of Bitcoin's main network effect generators of financial purposes. We can try to attack problem 1, although there is no perfect solution. IMO the goal should be to offer first "better" alternatives than Ordinals which do not generate spam conditions, like a data sidechain and OP_RETURN improvements, and only if the problem persists, then go and tighten rules (and @franky1: I sorta agree with you partially in your last post about rule tightening, although still - it's not my preferred way to act in this case, as the devs may have had their reasons allowing big taproot scripts).

--snip--

Your solution to 1st problem will not work. Various OP_RETURN[1] and sidechain based NFT already exist long time ago, but has very small userbase. In addition, Casey Rodarmor also state NFT user strongly prefer content stored on-chain due to various reasons[2].

Quote
as for those that want a bitcoin NFT where a file hash is showing a proof of transfer (thus no need of bitcoin being a meme library but just a timestamp proof of transfer of file hash NFT system. there is a simple way to do that using features over a decade old, which does not cause any mass bloat compared to average tx size
room for improvement for ordinals i guess? you're giving casey some ammunition there franky  say casey puts in a filehash for the subsequent transfers of the dead weight.  not that anyone would care they don't care about how it works just that it works, at least those bitcoin nft enthusiasts. they could care less how any of it works as long as they can see a picture of a monkey and other people agree they "own" it.

but they probably are smart enough to realize that their monkey can never "go away" unlike on ethereum where their monkey could possibly disappear oneday due to file hosting issues. they're that smart but no further.

Someone already attempt that by creating PR to support BitTorrent hash/magnet link[3]. But even if this PR is merged, i expect only small user would include BitTorrent magnet link instead since many NFT user prefer storing data on-chain[2].

[1] https://en.bitcoin.it/wiki/Colored_Coins
[2] https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021413.html
[3] https://github.com/casey/ord/pull/1805
1151  Local / Bahasa Indonesia (Indonesian) / Re: BITCOIN CORE on: March 13, 2023, 09:11:36 AM
Dulu kalau tidak salah, saya pernah tes menggunakan prune node atau testnet (lupa yang mana), namun intinya filesize dari blockchain Bitcoin yang sudah terdownload itu lebih besar dari rata-rata milik user lain. Waktu itu penasaran sampai di hapus dulu data blockchain yang sudah ada dan memulai download dari awal, namun filesize nya lebih kurang hampir serupa dengan yang sebelumnya.
Selain prune dan sebagainya, faktor apa saja yang membuat perbedaan setiap user?. Padahal kan ketika didownload masih dalam source yang sama yaitu bitcoin core wallet?. Apakah faktor OS, Hardisk dan Ram juga berpengaruh?. karena seingat saya dulu, ketika saya pernah ganti PC ke yang lebih tinggi spesifikasinya, memang ada sedikit perbedaan beberapa MB di bitcoin core folder.

Beberapa faktor yang saya ketahui,
1. Jumlah orphan/stale block yang disimpan oleh Bitcoin Core. Jumlah tersebut dipengaruhi oleh durasi waktu operasional Bitcoin Core.
2. Menyalakan index opsional seperti txindex.
3. Ketika Bitcoin Core ditutup, isi mempool dari RAM dipindah ke HDD/SSD.
1152  Local / Bahasa Indonesia (Indonesian) / Re: Mungkinkah untuk menambah Sub board lokal? on: March 11, 2023, 01:13:17 PM
Kalau dilihat dari jumlah request terbanyak sepertinya bisa dirangkum jadi tiga poin ini:

  • Mengubah nama child board Jual Beli menjadi Marketplace (Bahasa Indonesia)
  • Menambah child board baru bernama Trading dan Spekulasi
  • Menambah child board baru bernama Ekonomi, Politik, dan Budaya

Menurut saya lebih baik jika nama child board konsisten, dimana semua menggunakan bahasa Indonesia atau bahasa Inggris.

Opini saya:
Secara umum tidak ada concern dari saya pribadi. Usulan board di atas hanya seperti versi lokal dari board internasional. Trading dan Spekulasi = Speculation. Ekonomi, Politik, dan Budaya = gabungan Economics dan Politics & Society. Terkait CB Jual Beli saya setuju untuk diganti nama agar lebih jelas bahwa CB ini bukan hanya untuk jual beli, tetapi bisa menjadi tempat untuk thread diskusi exchanger dan layanan lain seperti keadaan sekarang. Untuk usulan CB khusus Bitcoin dan Pemula saya rasa ini bisa ditampung di SF utama dulu untuk saat ini.

Ada input?

Untuk diskusi Bitcoin and pemula, saya tidak keberatan jika ditampung di SF utama.
1153  Bitcoin / Mining / Re: America's first nuclear-powered bitcoin mining farm on: March 11, 2023, 01:01:26 PM
$0.02/kWh is extremely cheap. And if they really can achieve 5.5EH/s by 2nd quarter, they'll have about 1.5% of total Bitcoin hashrate. But i hope they'll be careful about expanding their business quickly since in past year many similar company went bankrupt.

If Nuclear Energy is cheap, why aren't we seeing widespread use of it as compared to fossil fuel?

Probably because high initial cost and push back from some environmentalist and people who afraid Chernobyl disaster will happen again.
1154  Bitcoin / Bitcoin Technical Support / Re: P2P trader gets into LN need help. on: March 11, 2023, 12:49:17 PM
1) My understanding is that LN is better suited for smaller tx, not so much for larger ones. Would it be a problem to send and receive 0.1 BTC on LN? What can I do to push back against those restrictions?

Many LN wallet have default 0.16BTC capacity, so you should able to send/receive 0.1BTC. However you could face routing problem since there aren't many LN channel with such big capacity, which force both party (you and buyer/seller) to make new channel instead.

2) I believe if you are not running your own node, your LN sats are all custodial. And my living situation doesn't allow me to run my own node. Is there a safe way to use someone else's node for a lot of coin coming in and out? Like 0.3 BTC per day, and 2 BTC per week?

There are light non-custodial LN wallet out there such as Electrum. But you either have to,
1. Run your own watchtower, usually on VPS.
2. Use someone else watchtower, either free or paid.

As reminder, watchtower is needed to prevent cheating by broadcasting earlier state of LN channel on Bitcoin on-chain network.
1155  Bitcoin / Development & Technical Discussion / Re: NFTs in the Bitcoin blockchain - Ordinal Theory on: March 11, 2023, 12:36:46 PM
Every 210,000 blocks. If you propose to just create 50BTC or 6.25BTC per block until 21M cap is reached, there are some reasons against that, e.g. that the limit will be reached quicker and we will still have the issue with what to do when there is no reward at all, just over 100 years earlier than with satoshi's model.
no i proposed to create a fixed block reward forever. be that 50 or 6.25btc that's something that could be decided on. then miners wouldn't need to have new sources of income like the ordinals trash. i'm sure a fixed block reward has been discussed ad-nauseum in the past though but in light of this new nft thing, maybe it need to be revisited.

While i see appeal of fixed/lower-bound mining reward, i doubt it'll happen when it violate principle of Bitcoin[1].

--snip--

So my issue is BTC is fucked without addressing this in only 33 years.

So No NFT + Ordinals to make up for this issue in the next 33 years. Okay

Unlikely to happen since censorship violate principle of Bitcoin[1]. At most Bitcoiner only can push to make Ordinal transaction with data bigger than X bytes become non-standard.

And no larger blocks to generate more fees. Okay

I believe it's just matter of time before we'll see increase of maximum block size when people realize other scaling solution isn't enough.

and LN that reduces fees and makes btc a partial POW. Okay

What does "partial PoW" even mean?

No recovery of stale unclaimed coins to keep rewards higher. okay

Technically possible. But i doubt there'll be middle ground about how should "stale unclaimed" coins is re-distributed.

No stretching block time to six years a ½ ing then 8 years a ½ ing . okay

This would break expected behavior of bitcoin transaction/address which use block height as it's timelock, including LN.

[1] https://en.bitcoin.it/wiki/Principles_of_Bitcoin
1156  Bitcoin / Bitcoin Discussion / Re: On Ordinals: Where do you stand? on: March 09, 2023, 12:11:00 PM
ok then pooya
seeing as many have tried to propose fixes for ordinal bloat and got no where
Have you got a example of this because if the proposed fixes bring more problems then fixes then I can see why they get rejected
If this had actually happened he would have filled bitcointalk about it instead of spreading misinformation with vague claims. As I pointed out above even if a PR is removed from BIPs repository it can not and will not be removed from the original repository of the person creating the PR.

I also barely found anything which could be count as "fix" towards Ordinal spam. Recently closed PR is either spam[1], duplicate[2], rejected modification[3] or self-closed without any response[4]. And it looks like GitHub doesn't let you delete PR, unless on very specific condition[5]. Even on bitcoin-dev mailing, there's only debate[6] rather than proposal.

[1] https://github.com/bitcoin/bips/pull/1409
[2] https://github.com/bitcoin/bips/pull/1426
[3] https://github.com/bitcoin/bips/pull/1297
[4] https://github.com/bitcoin/bips/pull/1419
[5] https://stackoverflow.com/a/18318431
[6] https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-February/021387.html
1157  Bitcoin / Development & Technical Discussion / Re: Look at this address and anwser this question on: March 08, 2023, 12:30:32 PM
19iAvuzfb8uH2SZLYcbb5wtbBZdn1o3vRm
And look at this tx:
d572c579f8de3c38b1dfab12928312fbe88f3d74a637d21a75b3f6d0510afe3a

there is a unknown sender called 1 of 1 multisig, ‎0.00010000 BTC

what shit is that?




It's old format address called P2MS[1]. If you see unknown, that means your wallet or block explorer missing few feature since you should see address such as "m-67202395617dc6a0a7e4eccba624f331".

[1] https://learnmeabitcoin.com/technical/p2ms
1158  Bitcoin / Development & Technical Discussion / Re: worried about downloading blockchain... on: March 08, 2023, 12:21:57 PM
Ok, I understand your point of view that is correct with the performacne. But I still think that it would be a good idea, at least if it is implemented correctly.
The encryption on HDD would always be optional, so that the user can decide whether to encrypt or not.
There should then be a switch in the settings.

In principle, it would be an optional additional function, which is even switched off via dafault.
The update would therefore not change anything for those who do not switch it on. You could even implement these things by plugIn.
Is there a plugIn API for the core?

Nothing would change the protocol. So it would be a simple change that would contain very few risk.

I agree it's good idea and would be nice if such feature is available. But looking at few old discussion[1-2], Bitcoin user/Bitcoin Core contributor had similar thought with mine. As for plugin, AFAIK such feature/API isn't exist.

[1] https://github.com/bitcoin/bitcoin/pull/46
[2] https://github.com/bitcoin/bitcoin/issues/9844
1159  Bitcoin / Bitcoin Discussion / Re: On Ordinals: Where do you stand? on: March 08, 2023, 11:18:24 AM
Actually anyone can do it (create new BIP), assuming they follow the guideline and receive some support or being very persistent. Some BIP 10x are result of being persistent. But i said "they" because improvement/change sometimes written by same person. For example BIP 173 (about Bech32) and BIP 350 (about Bech32m) have same primary author.

not everyone can "just create a bip"
first you have to pass a few tests of core demands for core to even acknowledge the bip as acceptable just to be listed

many bips get removed/revoked/not acknowledged and users banned because bips didnt follow the core roadmap

secondly even if you get your bip listed in the core github list of possible bips. this does not mean core will automatically commit to code then merge it into a release candidate. especially if the proposal opposes the core roadmap


as for the bech32 and bech32m. they are not simple edits of one proposal being persistant..
bech32 was segwit using witness version0 which is limited to certain segwit functions of opcodes,, and bech32m is for a different level of tx formats of witness v1 opcodes. for things like descriptors of taproot and such

but yes both segwit and taproot stuff was wrote by Pieter Wuille(and luke JR help) and yes both segwit and taproot ended up getting pushed into code with activated rules due to his insider circle of devs
and yes both segwit and taproot got activated without majority node readiness prior to activation and where both segwit and taproot were activated without finishing the code to make both formats secure and fully functional for their purpose/promise

1. What do you mean by pass few tests? Guideline on BIP 1/2? Something else?
2. I don't know about user got banned. But do you mean "Status: Rejected" or "Status: Withdrawn" when you mention said "many bips get removed/revoked/not acknowledged"?
3. Yes, it's true not all BIP will be implemented on Bitcoin Core.
4. I mention Bech32/Bech32m only as example of same primary author. For example of listed BIP due to persistence, BIP 100 to 109 should be better example.
1160  Bitcoin / Development & Technical Discussion / Re: worried about downloading blockchain... on: March 08, 2023, 09:46:25 AM
Quote
One could in a new core version,
Simply encrypted the blockchain with AES.
The own private key for the wallet would also be suitable as an AES key.
Then no government of the world could decipher its blockchain.

Apart from that, everyone who is afraid can simply encrypt their hard drive.


Does upcoming Bitcoin Core have such feature? Could you point link to discussion or pull request?

Not that I know of.
But I would welcome it if someone submits such a proposal and he is discussed.

I see. But it's hard to imagine such proposal would be accepted when it reduce performance (especially on HDD) and increase maintenance burden when they could just suggest user to use encrypted provided by OS or certain software.

One could in a new core version,
Simply encrypted the blockchain with AES.
The own private key for the wallet would also be suitable as an AES key.
Then no government of the world could decipher its blockchain.

Apart from that, everyone who is afraid can simply encrypt their hard drive.

Encrypt the blockchain data on your hard drive, how would other nodes read your encrypted data? If it's accessible for other nodes, it will be accessible to everyone, you can't hide/ lock the data if you want to maintain a node.

The data would be decrypted by full node software before it's being used for any purpose. So in practice other node doesn't even know your node store blockchain data in encrypted manner.

Yes, any government (especially authoritarian ones) could use any kind of excuse to justify their action. Although if they're not stupid, they should realize they only waste their resource since user can use VPN/Tor or even host it elsewhere.
OK, then the State-Attackers should find easier targets who are publicly known to run full nodes = Miners and Mining Pools.

Users above us already mention pool usually run on least hostile country while most miner don't run full node.
Pages: « 1 ... 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 [58] 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 ... 154 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!