What do you hope to gain by collecting posts of bad arguments / misinformation here in the choir space?

I've seen other posts here on the forum (I believe many are from you or you're at least a contributor) discussing threads on readdit etc. and people being set straight invitro, and that makes sense; it's a form of evangelism & marketing.

But here? What purpose do you have in mind?

Here is a good place to  start:   https://ieonline.microsoft.com/#ieslice

What is that? Any chance you can provide a URL that I don't have to opt into some MS bullshit?

Thanks!

It does seem like what's missing is how a domain owner can "give back" to the DAC and how that is measured. It should be a meaningful metric but not an onerous one. Most won't like it if "giving back" entails much effort or thought. About the only thing on my mind regarding an ICANN domain is when it expires and where I bought it.

The only things I can think of in terms of value add are more of a delegate type of function, like an ICANN to BitDNS bridge or search service or some type of rep system or rating service.

I'm quite impressed with your very methodical approach

The voting process is simpler than you imagine, you get P votes for each delegate, so your total voting power is simply P*101. Here's a quote from BM on the topic in another thread:

Quote from: bytemaster on September 15, 2014, 01:54:12 pm

With approval voting each individual can approve up to 101 delegates with their stake.  If you don't approve of a full slate (101) then you are effectively abstaining with 90% of your voting power.

Thanks cvk, I really appreciate that!

Couple of followup questions:

1) Regarding what you quoted BM saying, why did he say 90%, and why is it irrespective of how may delegates less than 101 I may choose not to vote for?

2) Can you confirm if these statements are correct:

Bitcoin minors simply look for the next prime number in a sequence (based on the agreed upon algorithm) and the first miner to find it and use it to encrypt (or sign) a transaction block is awarded the number of bitcoins for that era of the award schedule (50 initially, then 25 etc).

Bitshares delegates don't have to solve a CPU intensive task and race to sign a transaction block as with bitcoin. Rather, one of the 101 delegates is chosen in a random sequence to sign the next transaction block. The 101 delegates are chosen by popular vote of the DAC shareholders.

And is there a PTS DAC or is PTS the obsolete "ProtoShares" that have now evolved into the BTSX DAC?

What is the roadmap to going "live"? Will my BTSX shares have to be transferred to a new blockchain or will the current bc just evolve and grow as the toolkit code matures?

I'm trying to get on in real time for the first time today. I thought these were on Friday (today). In the past I've only listened to MP3s of them after the fact.

I'm trying to figure out the certificate thing. Do I just have mumble create a new one, or is there some type of linkage into bitshares authentication through the client? My mind is quick to link things when they're not always related, like crypto keys within the bitshares client and mumble certificates. Separate animals, right?

If I create a cert in mumble and provide name & email, why doesn't it ask for a password? If I try to connect mumble says "Wrong server password  for unregistered user account..."

What am I missing?

I am not aware of any 'secret' or delegate-only code in Bitshares X.
Now, *svk has done his share of coding to make this site, but the basic functionality comes from the  BTSX client itself...

You seemed to misunderstand. I never said or implied that anything was secret; I was only speculating about the code base required for delegates to fulfill their role. What you seem to be saying if I understand you correctly is that all of the functionality required to sign transactions and do everything on the bitshares network - examine blocks, get delegate stats, find users, send shares to other accounts etc etc, are built on a single toolkit. The same toolkit everyone has at their disposal is what svk used to obtain the info on his BitsharesBlock website. It's the same toolkit the client app is built upon.

That is good to know. If I want to get into those details I'll turn my attention to code development discussions, presumably found elsewhere here on this forum.

My only interest in such technical underpinnings right now is to understand how things work, in more detail than most discussions but less detail than looking at lines of code. I'm looking on the net now to find such intermediate info or possibly a bitcoin developer that could answer some of these basic blockchain oriented questions.

I do need to be cautious however b/c of the significant architectural differences between the bitcoin and bitshares networks. It might therefore be better to find someone like svk to discuss such things with, but I probably need to refine my questions and focus on specific things starting at the top and working my way down in detail.

I will state my apologies in advance and ask, is there a better place to be posting such questions? I don't wish to become a PITA as I learn this stuff. Fell free to point me elsewhere if you think my newbie questions are too basic or are already answered elsewhere.

Regarding the DPOS paper / website Daniel published on April 3rd linked above, I have some questions that span the range of the higher levels of abstraction down into lower (code oriented) levels.

In the background paragraph Daniel says there are two problems to solve: 1) selecting a unique node to produce the block and 2) making the ledger irreversible.

For bitcoin, producing a block is a computational algorithm of work performed by the miners. My understanding is that work is finding the next prime number in a cryptographic sequence such as SHA256 or SHA512 for example. How finding that relates to a transaction I'm not sure exactly.

I hear discussions that give me the impression transactions and the prime number searches are entirely separate things, yet other discussions where the prime number found is used to "sign" transactions. Does signing the transaction just mean to encrypt it with the prime number key? Is a signed transaction the same thing as a block on the blockchain, and the word blockchain and ledger are synonymous terms? If the transaction is encrypted (and thus it's contents private) does the blockchain include metadata for public info to support messaging, account registration / delegate info etc?

I'm pretty sure what Daniel is referring to when he says "selecting a unique node to produce the block" is what the delegates do in DPOS or who comes up with the longest series of signed transactions in the bitcoin network. The irreversibility problem relates to how much effort is represented by each subsequent transaction, such that going backwards in the chain to unlink those transactions essentially becomes impossible. Is my understanding of this correct?