996400+ entries in 0.734s
Diablo-D3: Im
talking
the actual mining units
Namjies: Did he sell
the whole 20000 shares
to get 200k?
Diablo-D3: okay so, did friedcat do preorders for his shit? or is he just selling
them straight?
mircea_popescu: what's
to debate ? just pointed out what
the contract said.
Diablo-D3: I
think you have
to wait
to see what friedcat is going
to do first
Namjies: Would you like
to debate
the point right away Mircea?
Namjies: It was a clause in
the contract.
Namjies: No,
the deal said should shares no longer be
tradeable, a
token payment of 1 BTC would be offered.
Diablo-D3: oh, so you
two just fucked shit up? lol.
mircea_popescu: Diablo-D3
this is about a private deal, not much
to do with friedcat really.
Diablo-D3: no I mean friedcat is already honoring
them even without
the lists
Diablo-D3: the shares dont go away because you cant
trade
them
Namjies: If shares don't start being
traded between people/on an exchange again, I was kissing goodbye
to over 1000 Asicminer shares
Diablo-D3: friedcat wants
to setup an exchange just for his assets
Namjies: [12:57] <Namjies> Mircea, you might actually have
to find someone
to buy ASICMINER shares from.
Namjies: [12:53] <Namjies> So... apparently, nefario started
to send out asset lists...
mod6: mircea_popescu: don't raise it before later
tonight lol
mod6: i better get one
tonight and heed my own advice.
mod6: DONT LET
THIS HAPPEN
TO YOU, SIGN UP NAO
mod6: i just haven't because i guess i didn't wanna step on my own
toes.
mod6: yeah,
to be honest, i actually meant
to make a new one like 50x before it went up
to 30.
mod6: oh ok, I'll just have
to make a new acct
then.
mod6: i guess in
the past i've had other pgp keys, i
think
they just expired and I made new ones...
mod6: haha, i'll have
to change
the expiration or whatever, no big deal
mod6: haha, i set mine
to expire in ...
mod6: haha,
thats awesome.
mircea_popescu: just letting you know
that you're gonna be working on
this well into 2015 lol
mod6: sure..i see what you're getting at.
these are great
things, looking forward
to
talking about
that more as
the
time comes.
jurov: you're welcome. while i just login
to coinbr and do stuff, having app would be nice.
mod6: i'll be stoked
to use it from
the car, or wherever. have you ever seen an MPEx
trade fly by on
twitter and wish you were home
to but in a bid? lol
mod6: and
then we have a first release. much more
to go from
there, but it'll allow a user
to
trade, send commands and see
the VWAP and Depth
mod6: just a screen
that displays
the results from
that
mod6: im so excited for
the JSONSTAT cmd,
thats
the only other
thing I need
to implement really.
jurov: or at least periodic fetching of new
transactions and notifying
the user
mod6: I honestly hope
to
turn BitOTTer into a fulltime
thing if all goes well.
mod6: I plan
to add charting and graphing and all kinds of neato stuff actually.
mod6: I see... very exciting feature
to be implemented for sure.
mod6: like atomated
trades?
jurov: of course, but it's necessary
to collect ideas. i'd also suggest scripting ability for paid version
mod6: at least
that was what was planned a while ago. I want
to kinda get a alpha/beta program going
mod6: Well, I had been wrestling with
this for a while, but what I
thought would be a good idea was if people use me for
the referal program at MPEx,
they can get BitOTTer
to download and also save some on
the MPEx registration as I'll kick
them back 2.5 BTC
jurov: and do you have some business model,
too?
jurov: yes, i appreciate
that effort
too
mod6: then put out
that alpha release I've been
talking about for forever. once
that happens, I can get some feed back from all
the users and make good changes based upon feeback
mod6: but... hitting some issues with getting
the private key back out -- hopefully I can whip up something different.
mod6: what i have code for now, and was
trying
to make work successfully was getting
these
three keys into a KeyStore for use as needed
mod6: and your MPEx private key should be vastly important
to you -- so
trying
to give
the user a layer of extra protection
mod6: oh for sure. it'll be risky
to probably keep any large amts on a mobile device
mircea_popescu: anyway, mod6 : all
this effort is not misplaced. I expect as bitcoins catch momentum
that iphones/etc will be stolen for
the btc content, much like wallets
today
mod6: currently
to
trade @ mpex you must be able
to clearsign,and enrypt a message - decryption is helpful
too!! -
this requires
the 3 keys I was
talking about
jurov: what? we're
talking about bitotter now, no?
mod6: and
then you can say, "THANKS MOD6!" instead of "FUUUUUUUUU MOD6!"
jurov: that means
two mpex accts?
mod6: i could write
that in also... anyway.
then
the key will be safe... at least it'll be encrypted if
the device is hacked/stolen
mod6: or
the user could do it if so desired
mod6: 4) notify
the user
to delete unencrypted private key file
mod6: 3a) encrypt private key and save output
to localfile store
mod6: 3) set
the seperate password for
the private key
mod6: 2) start BitOTTer and enter
the path's
to
the keys.
mod6: yeah, in
this situation
that im setting up for
the user,
the user will have
to do
this: 1) copy
the 3 pgp keys onto
the device
mod6: im using spongy castle
to read in
the PGP keys, I
then have
to convert
them
to be able
to use
them outside of its context, it gets hairy
mircea_popescu: you usually keep
the slut loaded, but periodically load
the safe one and move coins
there
mircea_popescu: jurov i
think maybe what he means is, have a sluttysally and a properpolly code.
mod6: then when
the user goes
to
trade,
they'll need
to enter
their passphrase
to decrypt
the encrypted private key stored on
the file system so
the application can decipher
the return
tx statements from mpex
jurov: you may find useful
to look into KeePass code
than
mod6: i don't want
to replace
the gpg passphrase... im saying
that
the user can set a seperate passphrase
to encrypt
the unencrypted privatekey file on
the filestore
mod6: huh? i
think we misunderstand eachother
jurov: you want
to improve over gpg passphrase? how?
mod6: use
that... maybe in a future release i can get
the keystore
thing working better, or change it so
the user might be able
to select from a variety of different algos
to use
mod6: what I was
thinking about using is currently a class
that implements 256bit AES
mod6: hmmm... well,
this wont be a 6 digit pin like
that
mod6: yeah, im not sure whatever Jan or whomever was
talking about. just want
to be clear about
that I'm doing :)
mod6: the code can read
them in either keyring format or ascii armor'd output format
mod6: the users PGP PublicKey and MPEx PublicKey can stay as
they are. no need
to do anything with
those at all.
mod6: ok.
to be a bit more spacific, and
the documentation will reflect
this... i'll encrypt
the private key on
the local file store.
mircea_popescu: <jurov> and upon pointed
to it, Jan proposed
to have
two keys on paper backup and alternate
them << lol
that one's good
mod6: anyway guys, I gotta run along
to something else quick. i'll
try
to save
the elaborations on
that for #BitOTTer in
the future.
thx.
mod6: its really getting close. i don't wanna let
this damn keystore hold me back when I can just use something else.
mod6: this will
take some
time, but I want
to get
this into
the hands of a few people who'd like
to
test it before
the end of
the year.
mod6: everything will be well documented in BitOTTer so
the users will know what
they are setting and what stuff means in
the application
mod6: i have a screen now where
the user goes in and sets
the private key for
the KeyStore, etc. but now I
think I'm just gonna make
that be
the symmetric key for like AES or something
jurov: i started
to be interested cause my phone got back from warranty prepair with completely replaced mobo
mod6: I wanna make sure
that if anyone uses BitOTTer
that
they know
their key
they put on
the device is safe at lesat if
the device is stolen or hacked
mod6: jurov: hmm! i didn't know
that.
they really should be just
to save a guy if his device gets stolen or hacked.
jurov: and upon pointed
to it, Jan proposed
to have
two keys on paper backup and alternate
them
mod6: right on. no matter what happens, I'll make sure
the PrivateKey ring file will be protected
jurov: mod6, bitcoinspinner does not encrypt
the keys at all