 Show Posts
|
|
Pages: [1] 2 »
|
|
How does this differ from other notary services that try to use the blockchain for this purpose ? This isn't addressed very well in the ANN. Not to mention, there is a bias against this type of use (non-financial data in blockchain), how do you plan to combat such criticisms?
|
|
|
|
|
I think there are a lot of developers in this space who are looking for the kind of work you proposed.
"Hack something up" and "2-3 days" are very mutual ideas so there is definitely some overlap between hacker/programmer culture and the finite space of ideas... If you could post a few more details about what the end result would be and who your demographics would be I'm sure some fine talented people will be knocking down your door to help.
|
|
|
|
Hey Bitcurex, have you considered adding an easier method for 2-factor authentication? I started using Clef recently and it was much safer (in my opinion) and easier to use than traditional methods like Google Auth and Authy. Would love to see this considered as an option for 2-factor on your platform. |
|
|
|
|
Pretty sure this could be a way to make 2 factor authentication easy for exchanges to implement, then maybe we will start seeing less of what happened to blockchain.info and others. Exchanges and wallet providers *need* a secure way to keep their login details from prying eyes, and as far as I can tell Clef is actually a solution. Bitstamp, Coinbase, you guys need to listen and pay attention here.
|
|
|
|
|
Really great listening to Greg last night, he was enthusiastic as ever about the project and in talking about Synereo's technicals! When I looked into this project there were several pieces that got me really excited, and the incentivization strategy (AMPs) combined with the promotion and social grouping (Reo) I think will make this project succeed. There are a few others who are attempting to provide a decentralized solution, but none of them are nearly as well thought out and put together as Synereo. Its the making of a successful project and definitely something I'm keeping a close eye on!
|
|
|
|
Looks like good material to be implemented, but too much delay and inactiveness
We've got a set of updates to roll out in the next few weeks with more detailed information about what Synereo will bring to social networking. We've been working incredibly diligently the last few months to bring together more materials to help our community understand what we're building. In contrast to other more mainstream social networks, Synereo is completely decentralized and is incentivized by a cryptocurrency. This represents our most recent developments which we have not had a chance to share with the community, and so we hope you can participate and join the discussion! |
|
|
|
Synereo has just released Chapter 2 of their network dynamics presentation! Chapter 2: Network Dynamics & Communities (Direct presentation link) Please join us in review of some of the key social and economic principles that underlie the Synereo vision: - Autonomous Synereos and communities - Reo and its influence over messages posted to the network - How Synereo's topology can be dynamically influenced - How user-created content moves and gains visibility across each Synereo In addition to those developments, there is further detail on how Synereo intends to manage privacy and arbitration in a decentralized social network that puts the community in control: - Opportunities to run communities that are self-governing and collaborative - Adminstration, arbitration and moderation policies - Privacy and identity controls - Island Synereos (great for teams and small communities!) If you've missed Chapter 1, this presentation explains the basics of Synereo, including Reo and how user-attention has an influence over the network: [ https://docs.google.com/presentation/d/12wZfRyF9XBMrc1ripXGfyNXCnO_MD7f2-Gc8AIa-v8o/pub?start=false&loop=false&slide=id.g4ecec4c43_3121 ] |
|
|
|
Hm, I'm curious, how or where are you getting the data to reconstruct the Armory tx? If you haven't looked at their code, I think this approach is perilous, since Armory's custom format will surely throw your code in disarray. For example, I'm not sure if the bytes from utxo's are appended like this: for coin in inputs:
tx_list += get_raw_transaction(coin['txid'], json=False)
for byte in range(0,len(tx_list),80):
txdp.append(tx_list[byte:byte+80] )
|
|
|
|
|
refund us man whats going on
|
|
|
|
|
"However, even if that was fixed, you still need the previous TxOut scripts in order to execute signing, which have to be retrieved from the blockchain -- again something else that Armory's TxDP structure bundles with it, but a raw unsigned tx from Bitcoin Core does not have."
I think you could make an additional query to the blockchain from bitcoin-core to find this info, AFAIK that is what we are doing now, but the answer to the above question is basically Armory has metadata that has to be fetched while online first, if going from bitcoin-core tx -> Armory tx
etothepi, could you let us know what exactly that info is?
|
|
|
|
|
cause you have to let armory sort out whether the input you selected is a valid (unspent) one or not
|
|
|
|
I hope the extra units will be added to increase current owner holding.
I think this is the case, as quoted from AKW above "release the *NEW* shares corresponding to PSUs" to me says he is selling additional share to cover the PSU's required for the new units. AKW may give current share owners first refusal on these additional share.
AKW, is the above correct? The new shares are to cover the cost of the PSU's for the additional units?
That was my reading of it too. I'm happy with the way AKW has managed this - it's been no easy task. My only reason for wanting to persue the refund path is simply that I do not believe anymore it will ever be profitable. Agree, refund |
|
|
|
|
this just saved me so hard.
thanks bootloads rbdrbd, keep doin yer thing,
great dev work
|
|
|
|
what are the middlecoin mirrors again? I'm down and need to round-robin it.
They're listed at the Middlecoin homepage now. Thanks. Will tip doge for that if you shoot me a PM with your address |
|
|
|
|
what are the middlecoin mirrors again? I'm down and need to round-robin it.
|
|
|
|
Is /wallet/send /wallet/pushtx and wallet/* implemented somewhere? I'm unable to locate the server code that handles these POST requests. Thanks Graz edit with reply from Grazcoin: Graz I'm then wondering, is there no reason to run server.py? Which .py file handles GET requests then? |
|
|
|
Faiz and I have been working with extending the existing webwallet that grazcoin and Grimentz have posted on masterchain.info. We've taken a crack at making a simple installer, and filled out installation instructions for the wallet, masterchain.info-style server, and obelisk server: https://github.com/LDEngine/msc-webwalletThe bulk of the Distributed Exchange specific stuff will come later - but I wanted to keep the project on people's radar. Faiz brought me on to help out with this web wallet ( https://github.com/LDEngine/msc-webwallet/). I contributed to early API design which was unfortunately abandoned. I helped Faiz with the client side encryption/decryption of private keys using HTML5 local storage I have been testing various new features and assisting with debugging/improvement I have started a fork to move the web wallet to django for maintainability as opposed to python's basic HTTP server Additionally to grok grazcoin's mastercoin-tools ( https://github.com/grazcoin/mastercoin-tools) I forked it and have started to write unit tests. I think Curtis and Patrick have said it better but we're working on a limited/zero trust web wallet for Mastercoin users. Right now we have client-side encryption, storage, and signing soon to come, and aside from that I think Grazcoin and Grimentz have done great work on their implementation and have been really helpful in getting us up to speed (we're using their fork). The UI will be developed in parallel of Marv Schnieder and Yuval's feedback as well to maximize the user experience of using Mastercoin. It is still in progress but as this is a bounty on reported progress I think it might be good just to inform others of where we stand. |
|
|
|
FROM PM: Thank you! && thank you all! -akw- This was me! Thanks for reposting. |
|
|
|
|
