Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - pc

Pages: 1 ... 77 78 79 80 81 82 83 [84] 85 86 87 88 89 90 91 ... 102
1246
Great plan, you have my votes!

(Disclaimer: I'm involved with Namecoin in that I maintain its linux packages.)

1247
General Discussion / Re: wallet.dat file from protoshares qt Help
« on: January 18, 2015, 04:13:27 pm »
how should he best claim:
1. His BTSX or BTS
2. His PTS or New PTS
3. Play or other Dacs

1. Import wallet.dat into BTS client: http://wiki.bitshares.org/index.php/BitShares/Howto#Attempting_a_wallet_import_to_receive_BTSX_from_February_28th_snapshot
2. Import wallet.dat into PTS-DPOS client (see http://pts.cubeconnex.com/wiki/index.php?title=Import_Keys_from_Wallet ). Or use the slightly more complicated wallet_import_by_signedmsg command.
3. Wait until launched, then import wallet.dat into Play (or other) client. For better security use import by signed message if available.

1248
General Discussion / Re: user issued bitassets dividend question
« on: January 16, 2015, 09:30:51 am »
Due to TITAN it is not possible to see which *user* owns specific assets.

But the assets are stored in the chain database with balance_ids, and these belong to an address. I. e. from a snapshot of the chain database you can compile a list of addresses and BLAH amounts and then pay out dividends to these addresses.

See also this thread: https://bitsharestalk.org/index.php?topic=13327.0

1249
General Discussion / Re: v 0.5 will be released today?
« on: January 14, 2015, 08:09:40 pm »
we are going around the DVS process specifically to get it out today.

-1

Oh boy.

1251
General Discussion / Re: Import PTS wallet from a year ago
« on: January 12, 2015, 05:27:00 pm »
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.

The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.

Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.

I get 3 different numbers. What is the difference between them?

My guess would be they are for DNS, AGS and PTS or something like that. Or for three different addresses? Anyway, in the end you should receive the sum of the three.

1252
General Discussion / Re: Import PTS wallet from a year ago
« on: January 12, 2015, 08:46:27 am »
No I did not have the before february 28. But I should receive some BTS (merger VOTE/DNS) because I had PTS during the november 5 snapshot?
I've read somewhere I am entitled to (amount of PTS @ november 5 x 567) BTS.

The BTS from the merger don't show up in your regular balance yet. You can check your shares by entering the command wallet_check_sharedrop in the console. You have to divide the displayed numbers by 100000 to get the BTS amount.

Also, the factor is much lower than 567, more like 45 or so. There's a thread somewhere in the forum that lists what you have to expect.

1253
If the client crashes or is otherwise forcefully terminated it is likely that the chain database was in an inconsistent state. In that case the client starts with an empty database again.

1254
Don't know about the decaying votes, but

A problem would be that if enough people don't start voting faster, then a smaller amount of stake would influence the vote more which makes it easier to vote in malicious delegates.  This would be another reason to separate block producers form employees so block producers can be voted in more slowly while employees get say a 2 week window after which its harder to vote them in.  There's also no reason to make employees have to wait 2 weeks to get their fee back, the block producers could inflate by default and the funds could be held in an escrow account which the voters control.  If the employee is voted in they could get access to the fee funds straight away and then have the rest released gradually as a vesting balance.  Having the voting as well as waiting to recoup the fee makes for a very slow and inefficient recruitment process.

Not to mention that having people pay a big fee to come onboard is not sustainable because it limits the talent pool we can grow form greatly, it will turn many skilled people away.  This could be solved by having no fee and instead having a recruitment delegate who is paid to vet the submissions.  He would transparently discard spam submissions and very weak applications and puts them in a viewable trash bin.  The applicants that make it past his basic appraisal can be voted on to become DAC employees.  This way there is no application fee.  We don't want an application fee because it deters talent.  The DACs income source should be its products not its recruitment mechanism, the fee beings a very small short term gain for a much bigger long term loss.  Again the block producers must be separated for this to work otherwise this is making it easier to become a block producer which is making it easier to attack the network by removing the fee and getting put into the 'fast track' voting channel with boosted fast votes. 

Having block producers + employees tied together means by making it more efficient to get hired you also make network attacks more efficient.  It may be hard for voters to keep up with with an extra layer of decision making, but not all voters are required for employee hiring.  Just those who want to be active in the DACs recruitment process would vote for employees.  Also that extra layer of decision making is already happening, just in a more muddled up way.

It could also allow people who just want to do a small project to apply for a specific amount of bitUSD.  Their application could be attached to a payrate so the escrow account controlled by voters releases only the amount of funds they applied for if they are voted in, allowing freelancers to do small jobs without having to pay an application fee.

I know focus needs to be kept on bringing stability to the client and not adding new features, but the current process very inefficient to the point of unsustainability.  A decentralised hiring process is an entirely new area BitShares is pioneering.  BitShares is in danger of innovating in too many areas at once.  I'm dependant on Riverhead for my delegate to run, most of the employees are dependent on other delegates running their delegate for them.  We may not like it but imo to thrive long term the process needs to be streamlined and separated out.  Perhaps something like this this could be tested out on Devshares in coming months and have a hard fork scheduled 6 months down the line to have a big upgrade to the recruitment system?

A potential employee should be able to just set their desired pay rate, make their application and press 'Go!'.  There should be no (big) fee, and no requirement to secure the blockchain.  It's not a top priority right now but I do think this needs improving.  We've got an amazing product with bit of an ugly 'internal corporate' structure, and we always should attend to our weaknesses.  I've heard that the Chinese aren't becoming delegates because a lot of them want to do just 1 project.  That's a lot of talent going to waste.  Lets cut the waste by empowering people to work for BitShares much more easily.  I know all of these suggestions together add up to a huge undertaking but its too important an issue to brush under the rug imo.  I think we're fine for the next 6 months-ish by using mainly in-house BitShares talent, but for longer term growth it needs to evolve.

This is just from the top of my head, feel free to shoot me down.

+1 !!!

Here's another reason for separating delegates + employees:
Depending on your jurisdiction, running a delegate includes a certain risk to violate fincancial regulatory laws. Working as an employee usually does not.

1255
Possible, yes, but also unlikely IMO.

As a simple test, fire up a miner of your own and see what happens - if the fan gets louder after a while it means that the system is not consuming much power *without* your own miner.

Have you made a quick plausibility check? I. e. multiply max power consumption of your computer with uptime - does that account for the increased power usage?

1256
BitShares PTS / Re: PTS vs BTS Snappshotting
« on: January 08, 2015, 08:13:14 pm »
One thing that would immediately clear my mind regarding PTS, is whether or not the snapshot for BTS went through (that BTSX was diluted so that PTS and AGS could be merged in, alongside vote and DNS).

If the dilution did occur, then isn't is a bit unfair that PTS would then continue to exist?...
Can anyone answer this? Was PTS merged into BTSX alongside DNS and VOTE as planned last year? Or did the community decide to allow PTS to exist on its own?
If it has been, then there is no reason for PTS to exist anymore.

We really should put this into an FAQ...

The merger on nov-5 merged DNS, VOTE and BTSX into the new BTS super-DAC. Because now the superDAC exists, I3 will not release any additional DACs. That change of plan was seen as unfair to PTS/AGS holders (post feb-28), which is why PTS and AGS also received additional BTS in the "merger". The social consensus remains unchanged wrt 3rd party DACs. Both Stan and Dan have repeatedly stated that PTS will continue to exist after nov-5.

1257
Deutsch (German) / Re: Delegates in D?
« on: January 08, 2015, 08:08:45 pm »
Wie kann man als delegierter ein gewerbe anmelden, wenn man niemandem eine rechnung stellen kann? wie soll man die "Einnahmen" rechtfertigen? Wie soll ich erklären wo die her kommen?

Das man Steuern zahlen muss ist klar, aber wie soll ich die angeben?

Ich glaube auf der Einnahmenseite besteht das Finanzamt nicht unbedingt auf Belegen... ;-) Im Ernst: schon die TX-History der Delegate-Wallet sollte im Zweifelsfall ausreichen.

Zum Thema USt habe ich eine neue Erkenntnis: man kann die USt gänzlich vermeiden, wenn man den Delegate nicht selbst betreibt sondern von jemanden im nicht-EU-Ausland betreiben lässt. Dem kann man dann z. B. monatlich eine Rechnung stellen, die er dann in BTS begleicht. Der Clou: bei "elektronisch erbrachten Dienstleistungen" für Kunden im nicht-EU-Ausland muss keine USt in Rechnung gestellt werden (siehe z. B. http://ec.europa.eu/taxation_customs/taxation/vat/how_vat_works/telecom/index_de.htm ).

1258
General Discussion / Re: Delegate slate publishing for non-delegates
« on: January 08, 2015, 05:11:06 pm »
I think what happens is this:

Everytime you vote for a combination of delegates that hasn't been voted for before, a new delegate slate is published. Subsequent transactions voting for the same delegate combination can then reference the resulting slate_id instead of including the whole list everytime. That's just the way voting works.

The tx contains several withdraws probably because someone wanted to vote with all their stake, which was distributed across several balance ids.

I'd also speculate that someone has published a delegate slate while simultaneously voting for a different combination of delegates, that's why there are two slates in the tx. But that's really just a wild guess.

Edit: just saw Vikram's answer.

1259
Depends on your environment. At home, blocking all outgoing connections is very uncommon. You normally want to use the internet, that's why you pay for it.

In a corporate environment it is not uncommon to allow only specific outgoing connections, for example through a reverse HTTP proxy.

1260
Unless your firewall disallows *outgoing* connections there shouldn't be a problem at all.

Pages: 1 ... 77 78 79 80 81 82 83 [84] 85 86 87 88 89 90 91 ... 102