Vladimir Marchenko [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2011-06-13 to 2012-07-15
💬 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 10:22:58

- reply

📅 Original date posted:2012-07-15
📝 Original message:Hi,
Why bitcoin.org promotes some private enterprises and not others?
May, I for example, have 20% of over the fold space on bitcoin.org
homepage for Bitcoin Magazine prmotions? Pretty please? </sarcasm>
Kind Regard,
Vladimir Marchenko.
On 15 July 2012 18:52, Amir Taaki <zgenjix at yahoo.com> wrote:
> Hi,
>
> Can I remove the hackathon from bitcoin.org and put up the conference instead?
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

2023-06-07 02:56:27

- reply

📅 Original date posted:2012-01-17
📝 Original message:On 17 January 2012 00:30, Amir Taaki <zgenjix at yahoo.com> wrote:
> ...
> Wikipedia has far more need to remain neutral and apolitical than bitcoin ever does- you've read Satoshi's politically charged whitepaper or seen the genesis block quote.
>
> http://en.wikipedia.org/wiki/Wikipedia:SOPA_initiative/Action
> ...
I would like to voice my support to Amir here. It is a solidarity
gesture and from my point of view it would be great if bitcoin related
websites join the Blackout. In my view it is almost like Internet's
general strike, which is being enacted for a very good reason. To some
degree, ignoring it and continuing business as usual is almost
equivalent to being a strikebreaker.
For whatever it worth, all websites where I have some degree of
control will particpate in the blackout. Even where it means loss of
revenue for one day (actually it is likely that ad revenues tomorrow
would be easily twice the usual amount due to so many publishers
shutting down their websites.)

2023-06-07 02:25:18

- reply

📅 Original date posted:2011-09-13
🗒️ Summary of this message: Bitcoin's code for time synchronization is a hack, but fixing it by incorporating an ntp library or removing mining code seems reasonable to experts.
📝 Original message:> 2) Bitcoin's "what time is it" code is kind of a hack.
...
> Fixing (2) is easier; incorporating a ntp library and/or simply
> removing the bitcoin mining code from the client but requiring pools
> and miners to have accurate-to-within-a-minute system clocks (or their
> blocks will be "discouraged") seems reasonable to me. If you want to
> produce blocks that the rest of the network will accept, run ntp on
> your system.
...
> --
> Gavin Andresen
>
As a miner I fully support route (2) and do not think that this would
cause any serious issues or discontent among miners. Most miners
surely are running ntpd already. Those who mess with the clock
intentionally will have to play ball.
--
Vladimir
-
http://bitcoin.org.uk/forums - clean and moderated bitcoin forum

2023-06-07 02:16:03

- reply

📅 Original date posted:2011-08-12
🗒️ Summary of this message: Bitcoin community portal launching soon at bitcoin.org.uk with advanced forum, blogging, calendar, and chat features. Invitation-only section for developers and support forums for businesses available.
📝 Original message:I am in a final stage of preparation for launch of bitcoin community
portal at https://bitcoin.org.uk . It contains fairly advanced forum
functionality, blogging platform, community calendar, and even chat.
Professionally hosted on highend dedicated servers running FreeBSD in
a DC loated in Amsterdaam, NL
There is a "by invitation only" section, which might be suitable for
bitcoin developers. Please consider starting using it and helping to
jump start it.
Additionally, if any bitcoin businesses would like to have their
"support" forums set up there so that they retail moderatorial control
over it please let me know.
Soft launch is scheduled on 15th of August, but it is fairly
functional already and open for registration. Feel free to register
and ping me for setting up appropriate permission for use of private
forums.
Any suggestions and feedback are also very welcome.
Kind Regards,
Vladimir.

2023-06-07 01:54:38

- reply

📅 Original date posted:2011-06-13
🗒️ Summary of this message: DNS bootstrapping can be made more robust by hosting seeds on services like Zerigo and small VPS, and using namecoin's TLDs to avoid centralization. A simple DNS server build and script can be published for anyone to host, and seeds can be hardcoded or conventionally pointed to bitcoin.* domains. However, there may be concerns about potential attacks from poisoned seeds.
📝 Original message:Jeff is absolutely correct, stating that DNS bootstrapping can
potentially be very robust.
Consider, for example, that seeds can be hosted by services like
zerigo, who provide decent management API's, as well as by thousands
of small VPS operated by people all over the world. Moreover, if
namecoin lives up to it's promises than some seeds can be hosted using
it's tlds, and as such we would get around centralised ICANN/registrar
weakness.
The most practical way I see how to improve DNS bootstrapping is
publishing build instructions for a simple DNS server build and a
script which feeds it with node data. Something simple like djbdns plus
a perl script, or similar zerigo API script, would do. Than anyone can
host it. All left to do than is to hardcode a bunch of such DNS seeds
into the client.
Hardcoding seeds is not good enough? Get a convention that anyone
owning a bitcoin.* domain should point seed.bitcoin.* to a decent DNS
seed. Than clients simply scan 100-200 tld's to find working
seed.bitcoin.*
I am not quite sure, though, is if this would enable some attacks by
poisoned seeds.
Vladimir.

2023-06-07 01:54:28

- reply

📅 Original date posted:2011-06-13
🗒️ Summary of this message: A possible bootstrap method for Bitcoin involves using a convention of bitcoind listening on a specific last octet of IPv4 address, .14 when possible. If no other method works, the client could start scanning x.x.x.14 addresses.
📝 Original message:one possible bootstrap method of last resort,
1. create a convention of bitcoind listening on a specific last octest
of IPv4 address, let's say, .14 when possible. Those of us who have
access to IP space would use .14's.
2. if no other bootstrap method works, client could start scanning
x.x.x.14 addresses, perhaps in some semi-intelligent order (starting
from more pobable /8's and /16's), if enough people place bitcoind on
x.x.x.14 than after a 10-100 thousand checks it bound to find a
bitcoind peer.
It's messy, with all the excessive scanning etc... but it does not
depend on anything except a bunch of bitcoind by convention preferring
listening on x.x.x.14's.
Given that this is a method of last resort in bootrap chain it whould
hopefully not lead to DDOS on those unlucky to own *.14 and not
running bitcoind there. Also the more people are running bitcoind on
.14, the quicker it would find a peer, the less scanning to do. It is
kind of self-regualting.
For whatever it worth...
On 13 June 2011 10:56, Jeff Garzik <jgarzik at exmulti.com> wrote:
> On Mon, Jun 13, 2011 at 5:38 AM, Christian Decker
> <decker.christian at gmail.com> wrote:
>> BitTorrent trackers are used to handle several thousands of requests, so
>> they would probably scale well enough. I'm not even talking about using the
>> DHT trackers, but using old fashioned HTTP based trackers. The fact that
>> each bitcoin client would contact the tracker would make it very hard for an
>> attacker to get bootstrapping clients to exclusively connect to his
>> compromised clients. I would say that using a tracker such as OpenBittorrent
>> provides the same advantages as using an IRC channel.
>
> And how does the client discover HTTP trackers? You're either
> hardcoding -those- into the client, or adding an additional bootstrap
> step to discover them. Either way, it has the same problems as other
> current methods.
>
> The history and experience of gnutella's web caches vs. UDP host
> caches seems highly relevant here.
>
> --
> Jeff Garzik
> exMULTI, Inc.
> jgarzik at exmulti.com
>
> ------------------------------------------------------------------------------
> EditLive Enterprise is the world's most technically advanced content
> authoring tool. Experience the power of Track Changes, Inline Image
> Editing and ensure content is compliant with Accessibility Checking.
> http://p.sf.net/sfu/ephox-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

- reply

- reply

- reply

- reply

- reply

- reply

{"author":"Vladimir Marchenko","date":"2011-06-13T18:00:59","text":"Jeff is absolutely correct, stating that DNS bootstrapping can\npotentially be very robust.\n\nConsider, for example, that seeds can be hosted by services like\nzerigo, who provide decent management API's, as well as by thousands\nof small VPS operated by people all over the world. Moreover, if\nnamecoin lives up to it's promises than some seeds can be hosted using\nit's tlds, and as such we would get around centralised ICANN/registrar\nweakness.\n\nThe most practical way I see how to improve DNS bootstrapping is\npublishing build instructions for a simple DNS server build and a\nscript which feeds it with node data. Something simple like djbdns plus\na perl script, or similar zerigo API script, would do. Than anyone can\nhost it. All left to do than is to hardcode a bunch of such DNS seeds\ninto the client.\n\nHardcoding seeds is not good enough? Get a convention that anyone\nowning a bitcoin.* domain should point seed.bitcoin.* to a decent DNS\nseed. Than clients simply scan 100-200 tld's to find working\nseed.bitcoin.*\n\nI am not quite sure, though, is if this would enable some attacks by\npoisoned seeds.\n\nVladimir.","summary":"📝 Summary of this message: \nDNS bootstrapping can be made more robust by hosting seeds on services like Zerigo and small VPS, and using namecoin's TLDs to avoid centralization. A simple DNS server build and script can be published for anyone to host, and seeds can be hardcoded or conventionally pointed to bitcoin.* domains. However, there may be concerns about potential attacks from poisoned seeds."}