Whitelist Requests (Want out of here?)

[M091]

Whitelist request.

I'm lurking around on this forum for a while now. I know the basics of Bitcoin mining, my main reason for joining Bitcointalk is using the marketplace subforum.

The holidays will be a lot happier if you accept my request

[1713584755]

1713584755

[1713584755]

1713584755

[1713584755]

1713584755

[1713584755]

1713584755

[1713584755]

1713584755

[1713584755]

1713584755

[lepirate]

Whitelist request!

I started earning bitcoins almost 3 months ago, read about it on different forums and followed whats happened on here at least the last months, and now I want to contribute!
I'll probably hang out most of my time (as I believe when writing this) at the General Discussion, but of course I might go to some other places sometimes!

[LateToTheParty]

Whitelist request.

I've been browsing the forums for a month or two, mainly reading up on the processing side of things.  I didn't realise there was a 4-hour restriction or I'd have joined sooner.

I'm fairly new to using bitcoins, but do have an understanding of the underlying protocol and hashing algorithm.

I'm currently experimenting with a home brew FPGA system.  I wish to participate in this thread; https://bitcointalk.org/index.php?topic=9047.0  (Official Open Source FPGA Bitcoin Miner)


Thanks

[BitcoinsAreFreedom]

Whitelist request!
I want to leave this sandbox where I cannot reply or post to anything of use!
Been working with bitcoins (more or less) for almost 6 months now!
Probably will I hang out at marketplace and the general discussion!

Thank you!

[Altos_]

I would like to be whitelisted for the Marketplace fourm so I can post in the "List of honest traders." thread.

I had a positive experience with a user of the fourm and would like to post for feedback.

[atifkhan]

I would like to request to be whitelisted as I intend to offer my ukash to bitcoin exchange services

[LateToTheParty]

Whitelist request.

Ignore that.  Just hit 4 hours.

[ThaddeusB]

No longer necessary

[scyth3]

I have been mining bitcoin for a period of time now. Not sure if that would qualify me to be whitelisted. Thanks

[nlovric]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

As the topic says.


Neven Lovrić


- --
Primary e-mail addresses:

• Internet: neven@lovric.net.
• Internet and Tor: nlovric@tormail.net.


Financial addresses:

• Bitcoin: 15eHztzh2YRFua3cBLWH8g87xm6tQ83FR3.


2012-04-11 OpenPGP public key:

• Internet: http://www.lovric.net/download/openpgppublickey/nlovric/2012-04-11.asc.
• Tor: http://li4znmlobepdaq4n.onion/download/openpgppublickey/nlovric/2012-04-11.asc.

• 7777 B191 5933 ACF1 B998  0101 70B9 7690 C7F8 DD31.


Latest OpenPGP public key:

• Internet: http://www.lovric.net/download/openpgppublickey/nlovric/latest.asc.
• Tor: http://li4znmlobepdaq4n.onion//download/openpgppublickey/nlovric/latest.asc.

• May be the 2012-04-11 key. Must be signed with the 2012-04-11 key.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIcBAEBCgAGBQJQ3F1LAAoJEHC5dpDH+N0xlWsQAI2WGianeA/g7bl3x8Q1amBt
WoddCtqdfSi1aLy4nlFL3vuQy4GsyRKA92air1Lnz6+MWjG2eCMlIZduDls4MiKi
CchPSKf3jLGRIYzgHsHf8XfdC/+7QNJoCmuEUCq9B2Aayzvmk3JXcBul+n/TKtfA
Q0pM1MXTLed75T2uFNaLyz8CDUMQGV+WfY6CxPlaEZVbNpO97lCFOuMsC+aInTTY
jj1bCi6YnPPhzoNZv8H3TRqJ6+FYYaToEyD/NqD32Y/54v6qP7Jc2/1UFmrKuPoX
gnbgYpyTvB01G48FrMworisE69hx/JQLdjygscHLdRSi5bMUBtlxNOafU6p9ZTxB
DKvMcAA2Aa6B8lxgw55XV/Db1ssXt17d4mmOy0zVdX+k0Nr/c9LTFqITJ3iKLUMo
RQh7cyljw+/ei5b61anc98GZTV5jr9ozuy8jkWv0SzSozTWabNjuGY7xH+9D9dpD
wLKgttSo20paJh2kH8mLH6tDoAd69OqmGKdShm7IAMx4VorkuGCOkcJ4oPqi2jNL
Oz06ypYbRWAzI6dQ+nFGDyQ1iemKL8koZBMTFw5Ju53kOBEGPlbVsbsPDHWyblkf
Bsj0vxx4HaAcpRqy67FHJEuwMC6lNDnOxdPU+SagOkCdF89y0dvrWDw+QXGPKPsV
dVNX/nHuo0oDHhEMvtKz
=M/BQ
-----END PGP SIGNATURE-----

[smtp]

Hi

Thanks to a personal email to a developper because after 20-30 mintes of lurcking around and see neither a repüly nor a new-topic button, his reply-email
 pointed me to the fact/politics of this newbie posting restriction.
THIS should be made clearly for each new registered account and then also be indicated which boards (or topics) are newbie postable, IMHO!

Greetings
smtp

[smtp]

Here is my posting/proposal to reason my request -- sorry for the bad style. :-/



Hi

The annoying huge real time to build up the blkindex.dat with the bitcoin-client is the trigger why I finally wrote this posting.
Sadly nowhere is explained neither which exact structure blkindex.dat has, nor
why we need this Berkley-DB-B-tree structure at all and it is extremly slow in
rebuild/updating in our case of bitcoin client.
Indeed I needed more than 23 h to build it from scratch with my 2 GHz Athlon-64 and 4 GB Ram. :-( and almost always the real time is spent by wait-for IO, not
CPU or network-band with limited if you want to catch up to the current blockchain.
Looking at the new bitcoin-client 0.7.99 test-release it looks still similar
slow, see benchmarks at [https://bitcointalk.org/index.php?topic=129861.0].
Thus I totaly agree in "We need to stabilize 0.8 as quickly as is reasonably possible, because people are beginning to avoid 0.7.x due to slowness, choosing instead less secure but faster bitcoin clients." stated by jgarzik in this thread.

I wonder why we need all this overhead-full and version-depending DB-stuff for
using/manipulating the blockchain in the bitcoin client. :-/

Here is an alternative for "blkindex.dat":

Hold the blockchain-indexing data always in memory and organize, it as follows:
Let there be TA-many transactions and DEP-many deposits (response-scripts/out-channels) in all the (valid) blocks in the blockchain.

On 2012-12-27 11:45 UTC we had #blocks= 213849, #TA =  10388275, #DEP = 24173524

The needed data structure consists of 2 tables and 1 heap:

1) A hashtable: we have TA many transactions and this number is steadily growing.
It is not decisive but I choose a hashtable which can store up to 2^26 many
 entries (so current fill-factor is < 1/6). Each transaction gets a 4 byte index, e.g.
made up of the lowest 4 bytes of a transaction-hash (or made by xoring the 32 bytes into 4
bytes) anded with 2^26-1 , ==> this is a 2^28 byte sized table, which each entry is either 0 or
indexs a further table, called transaction table for simplicity.

2) The transaction table has #TA*(32+2+8) bytes = #TA*42 bytes.
   Each entry of this transaction table holds ITS 256 bit doubled SHA-hashed hash = 32 bytes (back-check to the hashtable for index-collision-detection), a 2 byte counter (could be also 4 byte) for number of deposits and an 8-byte pointer into a heap for a specific transaction of a block of the blockchain.

3) the heap of deposit addresses and deposit values has size #DEP*(2*8+8) bytes
   Here the explicit value in Satoshis, the address of the script, and the
   address of the redeemed script is stored (null address if the deposit is
  still availible).
  The value of the deposits are pure luxury and could be saved. This value could
  also be goten from the address of the script decreased by 8. But I liked to
  store this value explicitly (in 8 bytes) and not looked it up each time in the
  blockchain.

The size of these 3 structures sum up to about 1285 Mbytes compared to 1481 Mbytes of the current blkindex.dat. The heap and the transaction table grows simply
by appending new data if new blocks are mined and published.
Searching for a transaction given by its 256-bit hashindex happens in constant time (depends only on the fill-factor of the hashtable) -- in contrast any B-tree needs log_2(#TA). Adding a new transaction with its deposits is of course proportional to the number of deposits involved.

Thus the real time needed to access a deposit is constant. There are the rare
events when we want to delete a orphan block and thus removing transactions with their deposits from our data structure. In this case, the needed real time is
at most proportional to the age of the orphan block respectively number of blocks in the part of the forked chain measured in number of deposits containing in the end part of the forked chain.
The average real-time behavior should be at least as fast as the old
"blkindex.dat"-logic, but probably much faster because we need no log_2-searching factor from the B-trees involved.

I implemented this logic/data structure already as part of a blockchain parser
and a total build up of this new "block-index structure" needed 242 sec real
time and 71 sec CPU-time - most time was spend in reading the blockchain from
disc. BTW: I did not optimize the source-code, already the 2nd program version
needs only these 4 minutes. I recall: Compared to more than 23 hours real time of the
bitcoin-client 0.7.1 needed to rebuild the blkindex.dat via "-loadblock" options. :-(

So the only draw back I currently see is a need of 1.28 GB Ram compared to at most 1/5-th (or less?) Ram in the bitcoin-client + 1.5 GB of blkindex.dat disc-space.
Omitting the Satoshi value of each deposit in the data structure and using only
a 2^25 sized hashtable (currently means a factor of 3.23 of total to used entries)
would result in 0.96 (0.13+0.44+0.39) GB Ram. Of course this data structure could be stored also on disk to avoid rebuilding each time the client starts.

The win is a real-time factor decrease of 350 -- and in absolute units from
many, many hours to a few minutes when building up the index data from scratch
in a bitcoin-client or whatever.  :-)

I like to hear your thoughts/critics.

BTW: If this is not too much nonsense perhaps a member could make a pointer to this posting in the thread/topic "Experimental pre-0.8 builds for testing" in the "Development & Technical Discussion"-board which is forbidden for newbies like me.

Thanks,
smtp

[AwkwardSituation]

I'd like out, been mining bitcoins since before D-Day (Drop Day from 50btc reward to 25btc reward) on our boy slush's mining pool.  I don't know how the whole infrastructure works for bitcoins, other than it's p2p encrypted virtual currency; still haven't googled why there are typically 8 servers my btc client connects to but meh. 

I can spout a bunch of googled technobable from the bitcoin wiki in here or you can just take me out of newbie land. Actually this may be my fourth post so maybe I met the criteria already

Anyway, awkward!

[Miles]

Hello I have completed my 5 posts, and have been online for 5 hours 54 minutes (actually have been a member for over a year now). Can I please upgrade so I can post normally.

[Arrowhead92]

I would like to be whitelisted as I am in need to sell some devices asap.

[querior]

Please whitelist me. I have a pending topic/question that I'd love to have moved to Technical Support.

https://bitcointalk.org/index.php?topic=133704.msg1423644

I'm just concerned it might not get enough eyeballs in Newbies.

Thanks for your time.
q

[ZMinner]

Hello,

I want to be whitelisted because i've already minned bitcoins and namecoins, i know how to use the bitcoin and namecoin clients and the guiminer and poclbm miners.
I m not interested in post on the newbie forum because I cant learn anything else as a newbie and i cant post on the spanish forum as a newbie.

[arnuschky]

Hey,

we're a group of researchers currently looking into Bitcoin from two angles: technologically, and economically (researchers as in University-level research).

We have been reading in this forum for 1-2 months now, and are well past the newbie state. We'd like to have full access so that we can ask specific questions in the appropriate sub-forums.

Thank you,
Arnuschky

[John (John K.)]

Hi

Thanks to a personal email to a developper because after 20-30 mintes of lurcking around and see neither a repüly nor a new-topic button, his reply-email
 pointed me to the fact/politics of this newbie posting restriction.
THIS should be made clearly for each new registered account and then also be indicated which boards (or topics) are newbie postable, IMHO!

Greetings
smtp

+1 if you hit the "yes I read it" button during the registration without actually reading any of it.

Had to go back to understand what was wrong...

Hello,

I want to be whitelisted because i've already minned bitcoins and namecoins, i know how to use the bitcoin and namecoin clients and the guiminer and poclbm miners.
I m not interested in post on the newbie forum because I cant learn anything else as a newbie and i cant post on the spanish forum as a newbie.

You can post at the Spanish forums already.

nlovric: OK
smtp: Already whitelisted
querior: OK
arnuschky: OK

[pizzaman1337]

Hello!

I've been a bitcoin user for a little while now, but I've only lurked on the forums, without an account.

I've been having a problem with campbx.com and I found a relevant thread I'd like to post in about it. This is that thread: https://bitcointalk.org/index.php?topic=133738.0

I don't really have anything to post about in the newbie area, the 5 post minimum seems to encourage spam. If I could be whitelisted, that would be great!

Thanks