Jay F [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2013-03-12 to 2013-08-03
💬 Posted a total of 6 messages
📚 Participated in the following categories: Bitcoin-development
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:05:29

- reply

📅 Original date posted:2013-08-03
📝 Original message:Namecoin already has an id/ and a/ (alias) namespace for such use:
{ "name" : "id/pichler", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 29397 },
{ "name" : "id/pigeons", "value" : "{ bitcoin:
1BekNv7ezkx8eAjdkrUta2BTp9bbxU9LGG, bitmessage:
BM-opfhTsUKdTezPiWFHxRQtM1ZMDvjKMkHf, ripple: rnziParaNb8nsU4aruQ
dwYE3j5jUcqjzFm}", "expires_in" : 10089 },
{ "name" : "id/pisces", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 32034 },
{ "name" : "id/plattler", "value" :
"\"BM-GtK6TiTtVo9toGVdk2zy3t4jGXZyZeMH\"", "expires_in" : 30999 },
{ "name" : "id/pope", "value" : "{\n \"bitmessage\" :
\"BM-2D7L1Suh1choaKt321Le3bS6PT6nxfWqpR\"\n}", "expires_in" : 29765 },
It's popular enough that it's been squat spammed by a few actors
recently, and several bitmessage IDs are there along with Bitcoin
addresses, etc.
On 8/2/2013 2:16 PM, Rick Wesson wrote:
> I'd raised this topic before suggesting to leverage DNS as its kinda
> useful for mapping names to numbers.
>
> Expect no support.
>
> -rick
>
> On Fri, Aug 2, 2013 at 1:40 PM, Chris Evans <aaxiomfinity at gmail.com
> <mailto:aaxiomfinity at gmail.com>> wrote:
>
> wonder if it would be good idea to have a alias to wallet id
> nameserver in the client software where a person can use a english
> name to describe a wallet public key address? and the software can
> use it to look up the wallet id.
>
> wallet ids are hard to remember/recall.
>
> -chris
> http://tawhakisoft.com/
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> <mailto:Bitcoin-development at lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

2023-06-07 15:01:39

- reply

📅 Original date posted:2013-05-12
📝 Original message:On 5/10/2013 8:39 AM, Gavin Andresen wrote:
> Bitcoin-Qt version 0.8.2 release candidate 1 is now available from:
> http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.2/test/
>
Testnet glitch, something broke...
Fired up 0.8.2rc, and .... where's the coins? Where's the blocks?
I get a new empty datadir/testnet3 subdirectory.
bitcoin-qt.exe -datadir=c:\testnet (with a testnet=1 bitcoin.conf file
option in that directory) stored wallet/blocks/chainstate in the root
with previous versions. Now the root datadir data is ignored (except the
config file) and a new hierarchy was created in subdirectory
[b]/testnet3[/b].
So what's happening?
This looks to be done by https://github.com/bitcoin/bitcoin/issues/2605
... after searching the code for the change and then finding the commit.
1 day from opened to committed, released six days later... no changelog.
The datadir previously worked as I expected with both bitcoin-qt and
bitcoind interacting with no problems, when simply specifying a
command-line datadir, so I don't see the bug.
I can see how the previous behavior might be dangerous if the config
file was removed. I just did that, and there's a cool freakout where my
testnet wallet balance looks like real BTC and Bitcoin tries to reorg
67662 blocks starting from the genesis block. After receiving real block
73354 per debug log, a nice unrecoverable crash:
"Assertion failed!"
File: src/main.cpp Line 1745
Expression: pfork != NULL
This needs to be added to the changelog, since dropping in this binary
will break testnet stuff if anybody is using Bitcoin this way for their
testnet faucet, etc:
" * testnet data now stored in testnet3 subdirectory, enforced even when
specifying datadir on command line (manually move your data first)"

2023-06-07 11:45:01

- reply

📅 Original date posted:2013-04-09
📝 Original message:On 4/9/2013 4:09 AM, Peter Todd wrote:
> On Tue, Apr 09, 2013 at 12:42:12PM +0200, Mike Hearn wrote:
>> hack by changing the protocol. Nodes can serve up blocks encrypted under a
>> random key. You only get the key when you finish the download. A blacklist
> NAK
>
> Makes bringing up a new node dependent on other nodes having consistent
> uptimes, particularly if you are on a low-bandwidth connection.
>
>> can apply to Bloom filtering such that transactions which are known to be
>> "abusive" require you to fully download the block rather than select the
>> transactions with a filter. This means that people can still access the
> NAK
>
> No blacklists
>
It depends on how clever the spammers get encoding stuff. If law
enforcement forensic tools can pull a jpeg header + child porn out of
the blockchain, then there's a problem that needs mitigation.

2023-06-07 11:41:16

- reply

📅 Original date posted:2013-03-23
📝 Original message:My first concern was that I and about everyone else only has TCP/UDP
port forwarding, but at least for the first:
UDT uses UDP to transfer bulk data with its own reliability control and
congestion control mechanisms. Multiple UDT flows can share a single UDP
port, thus a firewall can open only one UDP port for all UDT connections.
The latter appears not so friendly to NAT.
On 3/23/2013 3:30 PM, Mark Friedenbach wrote:
> If you're considering a datagram protocol, you might be interested in
> some more modern alternatives to UDP:
>
> UDT: Breaking the Data Transfer Bottleneck
> http://udt.sourceforge.net/
>
> Stream Control Transmission Protocol
> http://en.wikipedia.org/wiki/Stream_Control_Transmission_Protocol
>
>
>

2023-06-07 11:37:22

- reply

📅 Original date posted:2013-03-12
📝 Original message:On 3/12/2013 5:18 AM, Jorge Timón wrote:
> A related question...some people mentioned yesterday on #bitcoin-dev
> that 0.5 appeared to be compatible with 0.8.
> Was that only for the "fatal block" and would have forked 0.8 later
> too or is it something else?
> I'm having a hard time understanding this 0.5 thing, if someone can
> bring some light to it I would appreciate it.
>
> Thanks in advance
>
It was reported that not all 0.7 died from the BDB error either. This
will likely take a post-mortem to determine exactly what build
environments and versions are incompatible, by feeding each the bloated
block (hopefully there are lots of snapshots of the bad chain being the
best height for testing; I forgot to get one).