| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | AA | AB | AC | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Timestamp | All my work on the distributed exchange spec, code, and design: | All my work on the smart property spec, code, and prerequisites: | All my work on dEX testing: | Other work I would like considered for the "General Innovation" bounty: | Who are you? | BTC Address | MSC Address | |||||||||||||||||||||
2 | 2/28/2014 13:12:42 | Spec: Early in the month I started a discussion with Zathras and Grazcoin about a potential flaw in their handling of multisignature inputs. The discussion was brought about by my halting of the Masterchain website parser, and concluded with agreement on the removal of multisig inputs for Mastercoin transactions. This change was merged into the spec by Zathras and Marv at a later date, but its worth mentioning my code initially brought it to their attention, and would likely have been a security risk had the issue been found later. Code: Assisted in creation of a standalone python scripts to do simple sends, consensus calculations and balance checking. Open sourced code on Github and implemented those features from scratch to assist those moving off of mastercoin-explorer's deprecation and to assist in outside exchanges in implementing MSC on their exchange ANK.HK, Vault of Satoshi and others. I was assisting our point-of-contact with developing the virtual machine and ensured my code which was deployed worked in a production environment. The discussion with other exchanges is ongoing and our last contact included live-deploying these VMs along with usability testing, which I is ongoing and am a major part of. Over the past month (Since last payout) I've made over 90 commits and 27 pull requests to several Mastercoin repositories, adding many features that are critical to our wallet's continued operation as well as infastructure upgrades to other tools in the Mastercoin ecosystem. This includes API endpoint addition, server-side validation and business logic restructuring. Features that were added include a complete UI overhaul, sending transactions via client-side signing, and fast querying of address data. Design: I've worked closely with members of the Omniwallet team to ensure that the front-end design and architecture was top notch for our users. That included picking a framework that included out-of-the-box testing, client-side templating and robust support for UI elements crucial to providing a top-tier user experience for our Omniwallet users. I've also been a part of several discussions regarding overhaul of our back-end architecture as well, and with those discussions ongoing. | I've pinged Marv and he's responded that the spec is still being worked on "in specific". He has mentioned he will get back to me regarding this so that we may start building the tools and infastructure for Smart property. At this time I have not contributed much code or specification changes to the Smart Property features, however I have initiated discussion and I do hope to engage the leads on this issue after launch of the dEX. Note from J.R.: lots of wallet work! | Throughout working on the dEX featureset and Omniwallet in particular, I have been adamant about providing a concrete, defined and pleasing user experience. To that end I've asked friends to usability test and provide feedback on their experience using the wallet, which directly corresponds to code that I write that solves the particular pain point the user has. To that end, I've felt progress made on security of storing user wallets, accessibility of the interface towards new Mastercoin users, and professionalism in the look and feel of our interface. Discussions have been staged towards the end result of salting and hashing passwords in case of a leak, providing user affordances for areas of the wallet that seem burdened with complexity, and redesigning the layout of the interface to be more visually appealing to the eye. In the line of working on these things, I've also done real world usability testing with the creation of new Mastercoin transactions. I've created Simple Sends from various command line tools that I and others have created, as well as from our Omniwallet. More recently, I've been submitting Sale and Buy orders from our trading interface, which have proven valuable and show measurable progress in the real-world use of our wallet. These real world transactions show up on other implementations, and will be a barometer for the reliability of our software. | I've been working on various collaborative side projects for the General Innovation bounty that haven't seen an official release. In particular I'm working on a live order-book with Patrick (from Omniwallet) comparing the dEX and centralized exchanges such as masterXchange. The code is open source and viewable by all at https://github.com/faizkhan00/msc-orderbook/tree/new_master. I believe this could be a huge benefit to those traders seeking real time comparison of data feeds, and a financially interesting topic. In the end I do believe we might merge the code with Omniwallet, if there is demand for such a feature, but for now, it is a hack developed in my own time. | Faiz | |||||||||||||||||||||||
3 | 2/28/2014 14:13:45 | Did some Test MSC testing (sell offers) with Roman Mandeleil and Grazcoin on 23 JAN 2014. My btc add is 1MnPcdUFDYnTz3jz9n3erfWbd7JZfPunxL Regards, Colbert Lau, E: admin@bitcoinmalaysia.com | W : www.bitcoinmalaysia.com On 01/23/2014 09:49 PM, BM-2cXwikMGURpFu1s9SB2qpzGCVA7fzjPqSy@bitmessage.ch wrote: > This ERROR message is a known issue. A temporary hack, which should be > fixed hopefully today/tomorrow. > If you want to see the error also in this version, you could use chrome > developer tools and see the response of the server. Errors are there. > > I will check the logs to see your case. > Grazcoin > >> You know: what ever it is that error , >> the fact that the message >> is not so informative is a bug itself so >> I think we should document it somewhere >> but I don't know where exactly. >> >> >> On Thu, Jan 23, 2014 at 3:31 PM, colbert lau >> <bitcoinmalaysia@gmail.com>wrote: >> >>> Clicked Prepare and Source script still says "Error" >>> >>> weird >>> >>> cheers >>> colbert >>> >>> >>> >>> >>> On 01/23/2014 09:27 PM, Roman Mandeleil wrote: >>> >>> Hey it's the best stuff on the market !!! >>> >>> >>> On Thu, Jan 23, 2014 at 3:25 PM, colbert lau >>> <bitcoinmalaysia@gmail.com>wrote: >>> >>>> On 01/23/2014 08:43 PM, Roman Mandeleil wrote: >>>>> don't know, try to accept that one: >>>>> >>>>> >>>> https://masterchain.info/selloffer.html?tx=d2caf8a19b29959e1fe34dc7a499bddb6ee40fd3fb3fa23e4cc00b827e11b818¤cy=TMSC >>>> >>>> can u make it cheaper? >>>> lol >>>> >>>> price per coin to 0.00000010? >>>> >>>> -- >>>> Regards, >>>> Colbert Low, >>>> Executive Director, BTC INTERNET SERVICES (002210253-A) >>>> E: admin@bitcoinmalaysia.com | W : www.bitcoinmalaysia.com >>>> Secure Bitcoin Escrow Service - www.btc-asia.com >>>> Bitcoin Investor Group, http://bitangels.co/ >>>> >>>> >>>> >>> To unsubscribe from this group and stop receiving emails from it, send >>> an >>> email to dev+unsubscribe@mastercoin.org. >>> >>> >>> >>> -- >>> Regards, >>> Colbert Low, >>> Executive Director, BTC INTERNET SERVICES (002210253-A) >>> E: admin@bitcoinmalaysia.com | W : www.bitcoinmalaysia.com >>> Secure Bitcoin Escrow Service - www.btc-asia.com >>> Bitcoin Investor Group, http://bitangels.co/ >>> >>> >> >> To unsubscribe from this group and stop receiving emails from it, send an >> email to dev+unsubscribe@mastercoin.org. >> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to dev+unsubscribe@mastercoin.org. -- | Colbert Lau | 1MnPcdUFDYnTz3jz9n3erfWbd7JZfPunxL | |||||||||||||||||||||||||
4 | 3/1/2014 5:36:05 | Grimentz: * Implemented new full HTML5 wallet in demo.masterchain.info: https://demo.masterchain.info/wallet.html (users add addresses to wallet from address pages.) Currently supports >20 usability and security features and functions that facilitate DEx trading. Find detailed list in the next section. * Created quick user guide for the wallet available at: https://demo.masterchain.info/Masterchain_wallet_01.pdf Please read the user guide (it is just page) as it includes the full description of my main body of work. * Implemented HTML5 transaction form fully integrated with the wallet (import addresses and private keys from wallet) required for DEx testing. end-of-Grimentz | Note from J.R.: lots of wallet work! | Grimentz: I tested several standard DEx transaction dev.masterchain.info from the point of view of the wallet user: Initiated transactions from the wallet, verified that the transactions appear in the transaction history list of the wallet and reflected in the balance shown in the wallet. I continuously test the wallet of https://demo.masterchain.info/ on an array of >30 combinations of devices, screen sizes and resolutions and web browsers. As also the developer of the wallet I never move forward with design and implementation directions that cannot be scaled to all screen sizes and be usable with both touch screens and mouse modes. end-of-Grimentz | Grimentz: Started to investigate (working on a functioning prototype) an adaptation of the HTML5 web wallet into a standalone Android application (following a direct request from management) that can be executed directly without browser. I am using <WebView> control and it is going well (just started yesterday - on the 28th of February.) end-of-Grimentz | Grimentz | |||||||||||||||||||||||
5 | 3/3/2014 11:10:39 | Worked with Marv on Test Plan documentation layout and end tester interaction. Helped build/develop the form used by testers to report their test results. | None yet | Worked with Omni wallet team on vetting/verifying the implementation and deployment requirements/instructions. Deployed in test instance for a potential hosting company to review during which we identified build issues that required (short term: updated build instructions, long term: cloning support sub-repo's into a Mastercoin controlled sub-repo so we can update them to eliminate certain github related build issues. | Write up on mastercointalk.org with details about running Masterchest Wallet with alternate data directory. | Worked with Curtis to get VM with Toolset for 3rd party exchanges (ANX, VaultofSatoshi, Bitfinix, HolyTransaction,..) to use in integration testing and deployment of MSC. However most of the initial exchanges contacted have encountered delays due to the recent events in BTC and are still recovering/figuring out availability of time/resources. | Adam Chamely | 18hFjy7CWvX7FgZEXEW3bgz35KpYAzFR1c | 18hFjy7CWvX7FgZEXEW3bgz35KpYAzFR1c | |||||||||||||||||||||
6 | 3/2/2014 6:51:06 | Bitoy, Working on MyMastercoins.com website TMSC Consensus with MasterChest and MasterChain Released MyMastercoin Wallet version 2 source code and compiled version http://www.mymastercoins.com/MyMSCWallet.aspx Added support for Version and Action properties | Note from J.R.: lots of wallet work! | Created ViewAddressTrans for easier Dex consensus checking http://www.mymastercoins.com/ViewAddressTrans.aspx Sent 100 Dex 1BKpa19m5Xy9SvSzC5djPWtCfbuynSDwmb http://www.mymastercoins.com/ViewAddressTrans.aspx?Address=1BKpa19m5Xy9SvSzC5djPWtCfbuynSDwmb 39 Transactions 1EqTta1Rt8ixAA32DuC29oukbsSWU62qAV http://www.mymastercoins.com/ViewAddressTrans.aspx?Address=1EqTta1Rt8ixAA32DuC29oukbsSWU62qAV 13 Transactions 1QFWodNASZv8KRHnhypKaMys5CGRg7GrFQ http://www.mymastercoins.com/ViewAddressTrans.aspx?Address=1QFWodNASZv8KRHnhypKaMys5CGRg7GrFQ 11 Transactions 1GtTPepFqS8MWZzFKsE62bNowY2LZos8Lq http://www.mymastercoins.com/ViewAddressTrans.aspx?Address=1GtTPepFqS8MWZzFKsE62bNowY2LZos8Lq 5 Transactions | Bitoy | ||||||||||||||||||||||||
7 | 3/3/2014 13:00:20 | * major re-organization, clarification, enhancement of the spec - current/future transactions - transaction field definitions, valid values - transaction use cases that weren't addressed - added details and explicit descriptions for transaction behavior * helped resolve dev questions about what's correct tx behavior * reviewed/edited/approved proposed spec changes by others * reviewed OmniWallet UI, UX with Yuval, Curtis | * identified items in the SP spec that needed more detail and clarification * reviewed/edited/approved proposed SP spec changes by J.R. * proposed third-party SP rating/ranking service (like Moody's or Standard & Poors) - provide independently collected/verified trustable information about an SP and its issuer - a "standard" source for category, sub-category values (multi-lingual) | * whole content of https://github.com/mastercoin-MSC/QA - structure, guidelines, requirements for testing MSC applications - completed MastercoinDistributedExchangeTestPlan.md - wrote functional test requirements (>20 test procedures) for tx 0, 20, 22 - wrote test plan creation & test procedure customization process - wrote test plan execution process - wrote test results reporting form (w/ Adam Chamely) * tested OmniWallet initial release, submitted several UI/UX/functionality issues * investigated Crowdcurity.com for crowd-based testing | * my proposed third-party SP rating/ranking service is an important component in the eco-system - facilitates creation of cleaner, more standard SPs - gives consumers/buyers unbiased source(s) for info about SPs - it's fee-based, so it uses SP currency itself | marvschneider | |||||||||||||||||||||||
8 | 3/3/2014 15:12:24 | None | None | None | "Summary of work for Mastercointalk.org: - Installed Anti-Spam plugin (1365 Spammers blocked up until today) - Creating several sections - Cleaning the forum (Sticky, move, delete posts) - Referred over 10 members to mastercointalk - Created a countdown timer (http://mastercointalk.org/index.php?topic=108.msg284) - Approving and rejecting registered users noticed by the Anti-Spam filter (manually) - Helping lots of members with problems, also on Bitcointalk - Created child board for Meta to log the work for mastercointalk - Added development updates section and updated with all the weekly updates - Created tutorial (Send MSC) | jeroenn13 | 15EMewc1nH8Cqzsx8hrFNNdbQBjVTEWahp | 15EMewc1nH8Cqzsx8hrFNNdbQBjVTEWahp | |||||||||||||||||||||
9 | 3/3/2014 15:58:31 | For purposes of example I have named my entry for the general innovation bounty, “Coinvance”. I created the concept for Coinvance because I see a very large opportunity to solve an emerging problem that I see occurring within organizations and assets of those organizations. In high paced organizations within the cryptocurrency space we find that resources we need are often scattered and that there is no real central solution to publishing and archiving news, bounties, or initiatives for voting. Real-time group communication and collaboration through platforms such as Skype act as a home base where new ideas are born and further discussed in order to form solutions to problems that organizations face every day. I envision a future where each distributed organization has an easy way to centralize their communication while remaining as transparent as possible. During the month of February I worked on taking UI elements that I have from a previous project that I founded in 2013 and turning them into an organizational asset management platform aimed directly at the crypto space. My idea is that once decentralized apps and smart properties begin building atop the Master Protocol, a real need will arise for a user facing platform that facilitates collaboration, bounty, and voting management. Main Chat Screen. (https://dl.dropboxusercontent.com/u/45988033/preview/chat-regular.png) I believe that action within an organization starts at the level of group collaboration. That is why the focus of Coinvance is the chat screen. You can see on this screen that an organization/asset will be able to easily add in members of an organization to the chat and it will be possible for an admin(s) to assign their roles. Ideally roles/privileges will play an integral part in Coinvance. Those assigned an admin level within their organization/asset's chat will be able to sort the other members into groups. These groups/members will then be delegated their unique roles. For example, an organization that has a board, management, team members, advisors, and observers may want to place these individuals into groups that have certain powers such as news publishing, bounty creation, and voting rights. Further, some organizations may wish to assign power based on proof of stake. The Coinvance system will be setup in a way that the backend will be able to plug in with an exchange's wallet API and determine the amount of tokens one has for each asset that is using Coinvance. These numbers can be used when assigning proof of stake action items such as voting rights. Some other things to note from the left side panel of the chat screen is that there are also group chat rooms for each bounty and vote that takes place. Admins are able to easily bring in other team members, outside members from other organizations/assets, or the public to participate in collaboration surrounding a particular bounty or voting measure. Chat action split screen. (https://dl.dropboxusercontent.com/u/45988033/preview/chat-action.png) When a group discussion is occurring, the author of any particular chat message has the ability to click on a message and assign an action to it based on their privileges within the organization/asset. Any member that has been assigned the correct privileges has the ability to take a chat item and turn it into a public news item, a new bounty, or ask for a vote. Further, members of the chat will have the ability to easily like, tweet, or share their chat items to Facebook for publishing. The following screens will be built in the coming days and will function when members of a chat click on particular action icons from the split screen. News Publishing - A member of a chat will have the ability to take a chat item they have sent to the group and turn it into a public news item that anyone outside of the group chat will be able to see. These items will also show on the Coinvance newsfeeds of anyone following that organization/asset. Before the item gets published to the organization/asset's newsfeed, the author will be able to edit their original chat item. Text, pictures, video, and geolocation will be possible to add or edit to the post before it goes live to the public newsfeed. The public will have the ability to like or comment on these items. Bounty Publishing - Any chat item will also have the ability to become a public bounty. Like news publishing, the member creating a bounty out of a chat item will be able to edit their text, pictures, videos, geo, or attach other files to help better describe the bounty they need filled. Further, the reward(s) offered for the bounty will be assigned. Once a bounty has gone live, the author of the bounty will have the ability to add or invite other members within the organization or outside of the organization to the chat surrounding that bounty. Once the work is completed, the bounty will be divvied up by the creator of that bounty. Any new bounty that is created will show up on the public wall of that organization/asset and will also appear in the Coinvance newsfeed of anyone following that organization. Voting - Chat items will also have the actionable ability to be turned into votable measures for the organization/asset. When an a member of the organization/asset requests a vote, they will be able to edit their original chat message, assign pictures, videos, geo, attachments, etc. Further, they will also be able to assign an expiration date and also assign criteria that is voted on. More customization options will be provided including setting how they want each criteria rated (yes/no, 1-5, a percentage, etc). Finally, a member requesting a vote will be able to ask different groups within the organization/asset to vote on their measure (ex. board, management, devs, advisors, everyone, the public, etc). When members are assigned to vote on an item, they will receive a notification to do so. I ideally would like to add proof of stake voting in as an option here. Based on an exchange's wallet API, Coinvance would help members of an organization/asset determine the balance of tokens each member has. Based on these numbers, voting power for each member could be adjusted accordingly. Notifications. (https://dl.dropboxusercontent.com/u/45988033/preview/chat-notifications.png) Notifications will play an important role in driving action within an organization/asset. Each time a member adds a new member to a bounty, a vote, or tags them, he/she will be notified just like how most popular social sites work. Reminders will also be sent for outstanding action items like expiring opportunities to vote or deadlines approaching for bounties. Public screen. (https://dl.dropboxusercontent.com/u/45988033/preview/public-view.png) The public screen provides an organized front for an organization/asset. Viewers from the public or followers of the organization/asset have an easy way stay updated and interact with the organization/asset. Transparency is key here. The public will be able to easily keep up with the news, bounties, and voting results stemming from the collaboration within. Individuals from outside the organization/asset will be able to like things, leave comments, bid on public bounties, view internal voting results or vote on measures set to the public. Further, individuals from outside the organization will be able to like, comment, tweet, or share these items to Facebook. Monetization Model My idea for monetizing Coinvance is to issue leasable tokens that will each represent a member of an organization using Coinvance. Possession of these tokens will function as a license to use the system. Ideally these tokens would have an expiration date that is assignable to them. If the token expires, it is returned to Coinvance and the member's account is frozen from using the functionality of Coinvance. Further ideas for monetization include things like "bounty tokens" in which organizations utilize as a mechanism for rewarding members filling bounties within their asset/organization. These bounty tokens could be split up based on member participation or awarded based on how much of that member's work was used in the end solution. The house (Coinvance) would collect a small percentage of the overall bounty tokens for each completed bounty. | Ryan Keenan | 1PyQbHr3ywRdbkcq3sZKpkkJNBJUXbGXJH | 13NzZ7nwzEzLfuCEtfC1iQv5mJzs4PsFoW | ||||||||||||||||||||||||
10 | 3/4/2014 6:15:24 | DEx specific (dev): Full DEx update for mastercoin-tools / masterchain.info: https://bitcointalk.org/index.php?topic=292628.msg5344569#msg5344569 https://github.com/grazcoin/mastercoin-tools support of sell offers version 0000,0001 with actions New/Update/Cancel transaction version parsing: https://github.com/grazcoin/mastercoin-tools/commit/02f824ad21c09d510b34c0e2ca8abc97e53610c8 sell offer sub action https://github.com/grazcoin/mastercoin-tools/commit/2be9631d7d7e5f4fe23631fa0f946f301c6b9f09 update transaction version according to spec v0.4 https://github.com/grazcoin/mastercoin-tools/commit/c10f846d609a82af00238e833cf826cd5a037d20 DEx update for selloffer ver 1+0 new and cancel actions https://github.com/grazcoin/mastercoin-tools/commit/d07fce64451bef0c00e53f4fede4764dcdcf43ae add updating and updated_by fields to sell offer https://github.com/grazcoin/mastercoin-tools/commit/7421e09f9652f64d23fc7e3114379da4e58fbea7 validate cancel sell offer request https://github.com/grazcoin/mastercoin-tools/commit/14963071de3b53017016214dd98b3292ec84f1cb enable update sell offer for version 0000 https://github.com/grazcoin/mastercoin-tools/commit/19cca8a3d1ef7151bd5cead956c62b218a4a73da Raise issues of sell offers version 0000 validity and suggest alternatives: On email thread "Re: Invalidate all sell offers with version 0" discuss with bitoy correct generation of sell offer ver 0001 with New/Update/Cancel action field https://bitcointalk.org/index.php?topic=292628.msg5325891#msg5325891 https://bitcointalk.org/index.php?topic=292628.msg5296160#msg5296160 https://bitcointalk.org/index.php?topic=292628.msg5216037#msg5216037 https://bitcointalk.org/index.php?topic=292628.msg5186445#msg5186445 help getting to MSC consensus first: https://bitcointalk.org/index.php?topic=292628.msg5345204#msg5345204 discuss differences in parsing: https://bitcointalk.org/index.php?topic=292628.msg5382890#msg5382890 https://bitcointalk.org/index.php?topic=292628.msg5345204#msg5345204 + 16 emails discussing cases with Zathras/Bitoy on "Re: Consensus" thread on mailing list. + 8 emails on threads "Re: consensus issues on MSC" and "... on TMSC" and "DEx consensus". + ask to focus on 1BKpa19m5Xy9SvSzC5djPWtCfbuynSDwmb as the most complicated address. Explain parsing differences to bitoy https://bitcointalk.org/index.php?topic=292628.msg5450260#msg5450260 Explain Bitoy how to detect multisig input in his blockchain.info bases implementation on thread "Re: How to check if Multisig Input" in mailing list lobby against over payments feature https://bitcointalk.org/index.php?topic=292628.msg5450144#msg5450144 consensus updates reporter: https://bitcointalk.org/index.php?topic=292628.msg5360104#msg5360104 https://bitcointalk.org/index.php?topic=292628.msg5405621#msg5405621 https://bitcointalk.org/index.php?topic=292628.msg5435815#msg5435815 Consider also: Integrate the new wallet from grimentz https://demo.masterchain.info with masterchain-tools New wallet is already in use. You can find on https://blockchain.info/address/1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P already above 30 transactions using it (just look for dust 0.00005555) while until now it was only announced on the closed dev list. sneak preview on: https://masterchain.info/downloads/sneak_preview_wallet_local_usage.pdf Howto and tips: https://masterchain.info/downloads/Masterchain_wallet_01.pdf | No direct work, but forks: from competition rules on https://bitcointalk.org/index.php?topic=292628.0 "If somebody forks your code, and builds on it, you will get some consideration at payout time, even if you did nothing in the current contest." 2 forks fit to this rule: * curtis fork as mastercoin backend: https://github.com/grazcoin/mastercoin-tools/network https://github.com/curtislacy/mastercoin-tools * omniwallet uses web hybrid wallet infrastructure. https://github.com/mastercoin-MSC/omniwallet/ Note from J.R.: lots of wallet work! | Testing: Constantly check other implementation parsing, and alert on mistakes/issues. Create "tricky" transactions with sell offer update + over payment: https://masterchain.info/Address.html?addr=182osbPxCo88oaSX4ReJwUr9uAcchmJVaL¤cy=TMSC https://masterchain.info/Address.html?addr=17RVTF3vJzsuaGh7a94DFkg4msJ7FcBYgX¤cy=TMSC https://masterchain.info/selloffer.html?tx=65b106274aeae459290cdd4d2eba86b2c13b9b69f7aa5473aa5689a06443894d¤cy=TMSC https://masterchain.info/sellaccept.html?tx=9cc4651f4f844a2628800a23bce96a4738801c1c00e5a3aff95fc2d11041e501¤cy=TMSC https://masterchain.info/btcpayment.html?tx=6e77f3edf7afeb48a7f5315adc8bc42f7959af4925ed55adb336a2bd6048871f¤cy=TMSC Suggest interpretation of handling old TMSC sell orders from protocol ver 0.3.5 within ver 0.4: https://bitcointalk.org/index.php?topic=292628.msg5235610#msg5235610 https://bitcointalk.org/index.php?topic=292628.msg5234875#msg5234875 https://bitcointalk.org/index.php?topic=292628.msg5231545#msg5231545 Introduce consensus checkers for MSC/TMSC: https://masterchain.info/general/MSC-difference.txt https://masterchain.info/general/TMSC-difference.txt https://bitcointalk.org/index.php?topic=292628.msg5361780#msg5361780 support testers on masterchain.info testing thread: https://bitcointalk.org/index.php?topic=428798.msg4949332#msg4949332 https://bitcointalk.org/index.php?topic=428798.msg4903620#msg4903620 | Lobby against multisig multiple inputs (which was accepted): on "Re: multisig multiple inputs" thread on mailing list. Support Dominik's talk in Berlin with web wallet screenshots On email thread "Re: copyright of masterchain wallet" Integrate the new wallet from grimentz https://demo.masterchain.info with masterchain-tools New wallet is already in use. You can find on https://blockchain.info/address/1EXoDusjGwvnjZUyKkxZ4UHEf77z6A5S4P already above 30 transactions using it (just look for dust 0.00005555) while until now it was only announced on the closed dev list. sneak preview on: https://masterchain.info/downloads/sneak_preview_wallet_local_usage.pdf Howto and tips: https://masterchain.info/downloads/Masterchain_wallet_01.pdf Suggest a technical solution for Malability (agreed as good): "Re: Malability and Mastercoin" thread on mailing list. keep in mind that the idea of hybrid web wallet and the first implementation which was later forked. Now the omniwallet harvest the fruits of that innovation. Post deadline: prepare for curtis a branch with non-UI and flexible installation settings, on top of DEx code: https://github.com/grazcoin/mastercoin-tools/tree/json | grazcoin | 1CZ5WRYj48vWV7cYRRdheyhiodMVP3EMi3 | 1CZ5WRYj48vWV7cYRRdheyhiodMVP3EMi3 | |||||||||||||||||||||
11 | 3/4/2014 6:41:36 | Made a sellorder using Masterchain Webwallet: Transaction: e0280ad0b76d4fc436c58939d47934dea780f4c2cb052b1924d5490debdad16b https://masterchain.info/selloffer.html?tx=e0280ad0b76d4fc436c58939d47934dea780f4c2cb052b1924d5490debdad16b¤cy=TMSC Found some hard to use cases: https://bitcointalk.org/index.php?topic=428798.msg5505421#msg5505421 Tested the wallet, but had some problems to get it running. Synchronizing take way to long (over 36h). https://bitcointalk.org/index.php?topic=484025.msg5505109#msg5505109 | Tesca | 16BurP5f7n5RqjWGQ44Lj5NX6GzxaoAaqU | 16BurP5f7n5RqjWGQ44Lj5NX6GzxaoAaqU | ||||||||||||||||||||||||
12 | 3/4/2014 12:17:28 | Set all milestones, follow ups with devs to ensure delivery (all milestones met in March). Spec work: part of the discussion on edge-cases, multisig block (this release), conceptual development, advice and consent, including expected behavior Design work: early coordination on UI models presented by Yuval and Curtis' team, including direction and definition of audience. | Definition of the "kickstarter" method within the protocol. Several discussions with potential partners on use-cases, and definition of particular attributes to be included in the first several implementations. Gathered example smart property requirements from: Reggie Middleton and Mark Van Roon (dropped) Philip Potter (bitfinex) on creation/destruction/modification, call ability types, dividend needs and "tx fee"-style payments back to the issuer (and techniques to accomplish this) Steven Spague on device/user identity identification for trusted issuance and trusted transactions (this will be huge) Adam Joyce with Elliptic on financial contract writing definitions Adam Levine for user currency needs (LTBcoin for starters) Mark Karpeles on issuance of Goxcoin securitization of Gox balances | Successful recruitment: one tester, Shannon Code, and brought him up to speed to work with with Marv. (Shannon will be considered for RBB this month). Interviews with potential teams and candidates for testing and security, including CrowdCurity (Esben), and review of their testing reporting templates Coordination with Marv on reporting requirements per implementation, assigned the creation to Adam, provided to dev teams. | Preparation for the Texas hackathon including overview document, rules criteria (published) and a video interview for participants (Paul Snow). Further conceptual development on cross-blockchain MSC migration (think I've got it now!) including DEx functionality I will defer any General Innovation bounty reward I earn this month to Ryan Keenan for his work on the hackathon and his coinvance concept | Craig | |||||||||||||||||||||||
13 | 3/4/2014 14:47:43 | We are actively using the basic features of MSC (simple sends etc.) in production, and each time an issue arises with thoses features we actively seek support and advise the master protocol fondation regarding issues with the protocol. Also, we implemented a web based version of JR willet master adviser : https://masterxchange.com/advisor.php . This is a generic tool that we can give open source and maybe give to others website if they are interested in it. Right now it is locked in our address, but we could very easilly make a dynamic version of it if there is interest. | MasterXchange | 1zobh1SwsVdk3uMjEHeGV86hjNZeJ5CwC | 1zobh1SwsVdk3uMjEHeGV86hjNZeJ5CwC | ||||||||||||||||||||||||
14 | 3/4/2014 18:18:05 | My work in February was almost entirely on ommiwallet, which serves as a part of the base for dex, smart property, etc. February was dedicated primarily to the omniwallet UI. Features I implemented included: Document and clean up the API between the client and server. Switch UI dependencies so that they are managed by bower, rather than just checking in and managing js libraries manually. Display of BTC, MSC, and TMSC balances, and their approximate USD values. Extend the backend beyond what was inherited from master of tools to support lookup of BTC balances on addresses not included in MSC blockchain parsing. In addition to actual development work on omniwallet, I also produced and maintained the omniwallet demo server and vm image, which has been used in Adam's efforts to get MasterCoin integrated into other existing exchanges. I've also been guiding the omniwallet development team, through taskings, code reviews, and triage of bug reports. | Note from J.R.: lots of wallet work! | Curtis | 19TwBziBeCb4VnrZgJasJukwRKNSVvDp7Y | 13pm7cmA5vVpKkDLJCvqh26kcp6V6PJ1Aq | |||||||||||||||||||||||
15 | 3/4/2014 20:07:47 | My main role and contribution was in form of testing and providing suggestions for improvements as well as some proposed solutions for found issues. This is further summarized in "all my work on dEX testing". However, I'd like to mention that I found a way to gain full access to mymastercoins.com's database and immediantly made sure Bitoy is aware of this. (background: .NET binaries can be disassembled and the connection string was not encrypted). I submitted a proposal to remove the "reference address" in upcoming versions of the Master specification to allows things like multi send without creating complex new transactions: https://github.com/mastercoin-MSC/spec/issues/62 | None. :( | Primarily tested the Masterchest Wallet and Omniwallet with the focus of triggering unexpected behavior and ensuring basic functionality works as intended. Several test transactions were created of course. I use the Masterchain webwallet whenever I need to transfer MSC/TMSC, but it seems to be pretty well done already (except some minor issues). I'm also in a private email conversation with Bitoy about the MyMastercoins wallet to test his new implementations. Some results of the testing is documented in my GitHub activity in form of opened issues and comments: https://github.com/dexX7?tab=activity | A code snipped for an inefficient but working way to collect all unspent dust from Mastercoin multisignature transactions by using BitcoinRpcSharp: https://gist.github.com/dexX7/9146763 I grabbed coinwidget.com's famous donation button and added Mastercoin + added some functionality: http://mastercointalk.org/index.php?topic=141.0 Over the time the Mastercoin faucet was further improved by adding more authentication methods with a total of six now, while makeing absolutely sure those are not exploitable by creating many, many accounts. Some GUI improvements were made such as new, shiny buttons and a nicer "so, now that you have mastercoins, you can do this and that ..." landing page (http://imgur.com/a/QrPFs#0). I'm also very happy that my several SEO related optimizations (e.g. proper usage of keywords, tags, page speed etc.) were fruitful and created a significant gain in terms of search engine impressions and ranking: http://i.imgur.com/EDyrVTX.png | dexX | 11NiSNoGYomEA3ZHEN4R9ne4kwDjECsAy | 11NiSNoGYomEA3ZHEN4R9ne4kwDjECsAy | |||||||||||||||||||||
16 | 3/4/2014 22:52:56 | -Tested Masterchest.info (only reported 1 issue but it was already known) -tested Omniwallet (issue #54 already filed, issue #119, issue #120) -tested masterchain.info -helped masterchain.info setup a feedback widget -helped with omniwallet UI discussion | -Setup Mastercoin Foundation uservoice support service -helped setup uservoice widgets across websites -answered all support questions and tickets for Mastercoin -answered questions on forums -global mod on mastercointalk -made the ethereum research paper (snapshot of project condition) -made threads on reddit and bitcointalk about Dominik's mastercoinwallets.com (marketed on IRC's and tweeter) | Marin(Bebopzzz) | 15AnM1gg5HAAnRPPBUXFX1N6mbTt4cLyZJ | ||||||||||||||||||||||||
17 | 3/5/2014 8:22:24 | I've been security testing OmniWallet and going over secure implementations with the Dev team. I've also been collecting resources for creating a security bug bounty program and have a rough outline ready. | Shannon Code / Genecyber | 1N6vMzy46RNGny7u5BYMFGpPin7uW3cTKK | 1DMH2jezmNha2ShBhq3ogsXGviPBRppmwX | ||||||||||||||||||||||||
18 | 3/5/2014 9:29:59 | Helped testing Zathras' wallet. I did a TMSC-send and found some irregularity: https://bitcointalk.org/index.php?topic=484025.msg5488675#msg5488675 Tx-id: 9e52649ea61ad6d69c228c6b252d261fc6ae62fba25228c2c10a609f22969d90 | jakecnn | 1HXsrKJHbJCdWThFQL14tQ2ThuUhKUzmsf | 1HXsrKJHbJCdWThFQL14tQ2ThuUhKUzmsf | ||||||||||||||||||||||||
19 | 3/5/2014 10:45:58 | Code: I have been on Omniwallet team where most of my work in the last month has been concerning login, account creation, security around that, as well as creation of new btc/msc addresses. I have worked full stack on this, from backend to UI/UX in conjunction with the rest of the omniwallet team. Code stats put me at over 70 commits spread over 11 pull requests. Design: A big interest to me was the proper UX for the dEX on omniwallet, in which I spent a lot of time discussing with Yuval and thinking about his wireframes and just in general this is the thing I am most excited about. I can't wait to see how the dEX gets used by normal users and traders. | I unfortunately haven't had the time to think to much about the smart property feature other than reading the spec. Most of my work has been related to getting omniwallet implementing simple send/DEx features. Note from J.R.: lots of wallet work! | The omniwallet team did not get the UX/backend dEX components in place until last week but when we did, I began testing orders. Mainly to test out the functionality and UX of the omniwallet but also to test the general dEX functionality (and concensus with the other wallets). The entire month I have been on the project we actively test out our changes as well as the other team members changes. So for the omniwallet team I have especially tested out account creation, address import, seeing the correct balance and a lot of simple sends. Hopefully in the coming weeks we can do quite a bit more testing of the dEX as we build out that section of the site. We have worked with Marv in following his test plans as much as possible. (I would also love to implement some of those test plans as unit tests on our project but that may be after we get the initial release out) | I have some side projects in the works concerning the parts of the Mastercoin project that really interest me. I am working on an tool for Mastercoin traders and I do have the basic server but no frontend yet so maybe next time :) | azmenthe, Patrick Madden | 1EdtK7EkErgeU17qRuifxASA2yMoxibxYv | 1AQBeWsRfbHst7NojYdt42MZThcR4jy8fk | |||||||||||||||||||||
20 | 3/5/2014 15:09:43 | + Contributing to spec discussion and suggesting areas of ambiguity + Ongoing development of Masterchest Library + Ongoing development of Masterchest Wallet + Ongoing development of Masterchest Engine + Overhauled Masterchest DEx code accommodating all changes up to current spec revision + New library function encodepaytx for sending exchange payments + Initial versions of wallet released for end user testing (https://bitcointalk.org/index.php?topic=484025) + Contributing to project direction and development on various communication paths (email, skype etc) | + Ongoing development of Masterchest Library (prereq) + Ongoing development of Masterchest Wallet (prereq) + Ongoing development of Masterchest Engine (prereq) Note from J.R.: Lots of wallet work! | + Number of test DEx transactions + Maintaining consensus system for monitoring differences + Edge case testing (eg multiple/multisig inputs) + Reviewing differences in consensus & suggesting fixes + Various Masterchest Wallet, Library & Engine test runs & simulations etc + Bug resolution/discussion on issues raised during wallet testing | Zathras | ||||||||||||||||||||||||
21 | 3/9/2014 1:52:57 | ** This input is totally a summary for all February work I did. -- Helping Yuval to plane future UI of the, we have a discussion once/twice a week about the design he accoumplished and future UI development. | *** This input is totally a summary for all January - February work I did. + Testing of wallet 1 - masterchain.info - I have a coupled cooperation with masterchain.info creator (Graz), all the testing and improving we did is recorder in that thread (established by me in the end of January) https://bitcointalk.org/index.php?topic=428798.0 + Testing of wallet 2 - MyMastercoins Wallet working with the creator of the wallet (Bitbay) on the testing and user experience. https://bitcointalk.org/index.php?topic=355739.msg4641111#msg4641111 | *** This input is totally a summary for all February work I did. +Translating for Hebrew wiki: http://goo.gl/t1V3Pa | Roman | 1RomanPitS8Xq1KV6tUr67zMrxnvGEzWb | |||||||||||||||||||||||
22 | 3/18/2014 14:57:48 | ||||||||||||||||||||||||||||
23 | 3/30/2014 1:40:39 | I was making 10-15 hrs discussion with Yuval about design and user experience | Here is all issues I was working on, I am marking: (+) - added issue , (V) - verified issue, (X) - verified and rejected issue (V) https://github.com/mastercoin-MSC/omniwallet/issues/241 (V) https://github.com/mastercoin-MSC/omniwallet/issues/281 (V) https://github.com/mastercoin-MSC/omniwallet/issues/217 (V) https://github.com/mastercoin-MSC/omniwallet/issues/120 (+) https://github.com/mastercoin-MSC/omniwallet/issues/280 (+) https://github.com/mastercoin-MSC/omniwallet/issues/281 (+) https://github.com/mastercoin-MSC/omniwallet/issues/282 (+) https://github.com/mastercoin-MSC/omniwallet/issues/283 (+) https://github.com/mastercoin-MSC/omniwallet/issues/284 (V) https://github.com/mastercoin-MSC/omniwallet/issues/261 (V) https://github.com/mastercoin-MSC/omniwallet/issues/236 (V) https://github.com/mastercoin-MSC/omniwallet/issues/264 (V) https://github.com/mastercoin-MSC/omniwallet/issues/274 (V) https://github.com/mastercoin-MSC/omniwallet/issues/208 (V) https://github.com/mastercoin-MSC/omniwallet/issues/254 (V) https://github.com/mastercoin-MSC/omniwallet/issues/281 (V) https://github.com/mastercoin-MSC/omniwallet/issues/192 (V) https://github.com/mastercoin-MSC/omniwallet/issues/254 (X) https://github.com/mastercoin-MSC/omniwallet/issues/246 (V) https://github.com/mastercoin-MSC/omniwallet/issues/240 (V) https://github.com/mastercoin-MSC/omniwallet/pull/226 | Roman | 1RomanPitS8Xq1KV6tUr67zMrxnvGEzWb | ||||||||||||||||||||||||
24 | 5/7/2014 8:54:21 | ** study of current working code and specification - daily activity ** Actively establishing working knowledge of code for design and deployment. ** I need to go full time on current design. | ** Building widget to handle property lookups | I will graph out my results from database when I have more time. I am working 12 hour shifts driving forklift at work and need to shift out so I can let my 30 years of computer experience shine. -- I will have testing results relayed upon discovery. | General Innovation Details: ** VM Online and Working for current developers to connect and test ** Security Audit layer established for verification of developer transactions ** OracleVM establishment ** MS-SQL Deployment on VM ** Layout and Security of smart property look-up tables ** Initial Design of Service Application to handle transactions from weblayer ** Security testing of VM ** Building of automation tools and reports for testing ** Intraweb Service app Development in Delphi ** Unity3D wallet in design. ** C# Classes for handling api requests in backend of app. ** Android / IOS deployment of app via: Unity3D I have a wide spectrum of technical knowledge and I will bring it all to the table for the project. my referal is 604Joe has given me the thumbs up to get involved. I have been writing code under Skyboard Software. I will continue working on security and bug tracking. | burndata | 1A6VMUe1psefZiz3f1Xwzmzn4MQcvq5zpR | 1A6VMUe1psefZiz3f1Xwzmzn4MQcvq5zpR | |||||||||||||||||||||
25 | |||||||||||||||||||||||||||||
26 | |||||||||||||||||||||||||||||
27 | |||||||||||||||||||||||||||||
28 | |||||||||||||||||||||||||||||
29 | |||||||||||||||||||||||||||||
30 | |||||||||||||||||||||||||||||
31 | |||||||||||||||||||||||||||||
32 | |||||||||||||||||||||||||||||
33 | |||||||||||||||||||||||||||||
34 | |||||||||||||||||||||||||||||
35 | |||||||||||||||||||||||||||||
36 | |||||||||||||||||||||||||||||
37 | |||||||||||||||||||||||||||||
38 | |||||||||||||||||||||||||||||
39 | |||||||||||||||||||||||||||||
40 | |||||||||||||||||||||||||||||
41 | |||||||||||||||||||||||||||||
42 | |||||||||||||||||||||||||||||
43 | |||||||||||||||||||||||||||||
44 | |||||||||||||||||||||||||||||
45 | |||||||||||||||||||||||||||||
46 | |||||||||||||||||||||||||||||
47 | |||||||||||||||||||||||||||||
48 | |||||||||||||||||||||||||||||
49 | |||||||||||||||||||||||||||||
50 | |||||||||||||||||||||||||||||
51 | |||||||||||||||||||||||||||||
52 | |||||||||||||||||||||||||||||
53 | |||||||||||||||||||||||||||||
54 | |||||||||||||||||||||||||||||
55 | |||||||||||||||||||||||||||||
56 | |||||||||||||||||||||||||||||
57 | |||||||||||||||||||||||||||||
58 | |||||||||||||||||||||||||||||
59 | |||||||||||||||||||||||||||||
60 | |||||||||||||||||||||||||||||
61 | |||||||||||||||||||||||||||||
62 | |||||||||||||||||||||||||||||
63 | |||||||||||||||||||||||||||||
64 | |||||||||||||||||||||||||||||
65 | |||||||||||||||||||||||||||||
66 | |||||||||||||||||||||||||||||
67 | |||||||||||||||||||||||||||||
68 | |||||||||||||||||||||||||||||
69 | |||||||||||||||||||||||||||||
70 | |||||||||||||||||||||||||||||
71 | |||||||||||||||||||||||||||||
72 | |||||||||||||||||||||||||||||
73 | |||||||||||||||||||||||||||||
74 | |||||||||||||||||||||||||||||
75 | |||||||||||||||||||||||||||||
76 | |||||||||||||||||||||||||||||
77 | |||||||||||||||||||||||||||||
78 | |||||||||||||||||||||||||||||
79 | |||||||||||||||||||||||||||||
80 | |||||||||||||||||||||||||||||
81 | |||||||||||||||||||||||||||||
82 | |||||||||||||||||||||||||||||
83 | |||||||||||||||||||||||||||||
84 | |||||||||||||||||||||||||||||
85 | |||||||||||||||||||||||||||||
86 | |||||||||||||||||||||||||||||
87 | |||||||||||||||||||||||||||||
88 | |||||||||||||||||||||||||||||
89 | |||||||||||||||||||||||||||||
90 | |||||||||||||||||||||||||||||
91 | |||||||||||||||||||||||||||||
92 | |||||||||||||||||||||||||||||
93 | |||||||||||||||||||||||||||||
94 | |||||||||||||||||||||||||||||
95 | |||||||||||||||||||||||||||||
96 | |||||||||||||||||||||||||||||
97 | |||||||||||||||||||||||||||||
98 | |||||||||||||||||||||||||||||
99 | |||||||||||||||||||||||||||||
100 |