From 0af0861599b6d4c11c7a5109a242d4d47e650063 Mon Sep 17 00:00:00 2001 From: Riccardo Spagni Date: Tue, 22 Mar 2016 15:12:32 +0200 Subject: [PATCH] update binaries to 0.9.3 --- _data/downloads.yml | 36 +-- ...-for-the-dev-meeting-held-on-2016-03-05.md | 231 ------------------ downloads/hashes.txt | 26 +- downloads/index.md | 2 +- 4 files changed, 33 insertions(+), 262 deletions(-) delete mode 100644 _posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md diff --git a/_data/downloads.yml b/_data/downloads.yml index 98ee6c4c..4d7ac696 100644 --- a/_data/downloads.yml +++ b/_data/downloads.yml @@ -1,48 +1,48 @@ - platform: Windows, 64-bit icon: windows.svg url: win64 - hash: 303840d7fb997b2f1efc280fd19ba84003ecff85 - version: 0.9.1.0 + hash: 246115b0da133e0203dc78d26bbc82e9b76a178939bff8d4541bf04a02a19854 + version: 0.9.3.0 tag: Hydrogen Helix blockchain: win - platform: Windows, 32-bit icon: windows.svg url: win32 - hash: none - version: 0.9.1.0 + hash: 4663222a810ad854da1fc9d665e51252e61ddb1a8f69de3a31ad195386d445a2 + version: 0.9.3.0 tag: Hydrogen Helix blockchain: win - platform: Mac OS X, 64-bit icon: apple.svg url: mac64 - hash: d6c776878fd3d47f149fc9be4e76cf2d03d5a725 - version: 0.9.1.0 + hash: f471a420485413d5fcb1b19065a3b4e9a68c49596ddd6291787ad34121bad32c + version: 0.9.3.0 tag: Hydrogen Helix blockchain: mac - platform: Linux, 64-bit icon: linux.svg url: linux64 - hash: 4149de91c10b56ff091070acca80d233fbd5a797 - version: 0.9.1.0 + hash: 9e6747b69642389e98ca5f70cec7276f7af7156e5dce95409a8da7cccff5876e + version: 0.9.3.0 tag: Hydrogen Helix blockchain: linux -- platform: FreeBSD, 64-bit - icon: freebsd.svg - url: freebsd64 - hash: 9fd0005b697e146a26a0bf9e3cd0c89b978f7fbd - version: 0.8.8.6 - tag: Release - blockchain: freebsd +- platform: Linux, 32-bit + icon: linux.svg + url: linux32 + hash: 90c51c4a68f78ac2262a7b5a676f02d43ba7b9b6800b8b150d89980604c969f2 + version: 0.9.3.0 + tag: Hydrogen Helix + blockchain: linux -- platform: Raspberry Pi / ARM +- platform: ARMv7 icon: arm.svg url: arm - hash: none - version: 0.9.1.0 + hash: c312ba0810bf04ab2e28b61a50de2a83c1c614fd789bab4cacacb716134a7239 + version: 0.9.3.0 tag: Hydrogen Helix blockchain: arm diff --git a/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md b/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md deleted file mode 100644 index c42f795d..00000000 --- a/_posts/2016-03-05-overview-and-logs-for-the-dev-meeting-held-on-2016-03-05.md +++ /dev/null @@ -1,231 +0,0 @@ ---- -layout: post -title: Overview and Logs for the Dev Meeting Held on 2016-03-05 -summary: Clarification on ringCT next steps, Trezor integration status, net_skeleton replacement -tags: [dev diaries, core, crypto] -author: gingeropolous ---- - -*March 5th, 2016* - -# Logs - -**\** dev meeeeeeeting -**\** role call -**\** ping -**\** no problem :) -**\** hyc / moneromooo / warptangent / luigi1112 / smooth -**\** smooth, luigi1112, othe, NoodleDoodle, ArticMine, warptangent, moneromooo, hyc -**\** pingping -**\** or any other luigi's -**\** present -**\** my body is here too -**\** present -**\** lol -**\** othe: but your mind is... ? -**\** ok let's start -**\** i dont know where it is fluffypony -**\** er, hi ? -**\** open pull requests: mostly just DB stuff by warptangent and hyc -**\** will be merged within the next couple of hours -**\** ok -**\** how are you guys? -**\** glad for the weekend -**\** merged pull requests in the last couple of weeks: unit test fixes, threading fixes, lots of little things -**\** I suppose the big stuff is hyc's readtxn changes -**\** is the exp/performance stuff from warptangent also to be merged in? -**\** warptangent / moneromooo: do one of you want to give us an overview of readtxn? -**\** not soon -**\** and should we add the trezor support from NoodleDoodle ? -**\** othe: we're doing PR review first -**\** the txn cursors enable lmdb to read and write more efficiently -**\** hyc added write cursors and then read cursors to cover just about all the DB operations -**\** cool -**\** re: warptangent's performance changes -**\** we have to implement some sort of migration system -**\** we can't expect people in production to keep dropping and re-syncing -**\** so that would stall it being merged -**\** hi, sorry I'm late. our experience with blockchain_import indicates migration will be slow -**\** also, migration won't take place until after things settle with the db changes and testing. -**\** development is ongoing here https://github.com/warptangent/bitmonero/branches in the exp/performance branch -**\** hyc: well at the very least we need to detect that the current DB isn't what we expect, and that it must be converted or redownloaded -**\** \*resynced -**\** right. well fortunately the DBs have version stamps so that's straightforward -**\** yeah -**\** ok let's move on to trezor -**\** NoodleDoodle: are your changes stable enough to PR? -**fluffypony** plays elevator hold music -**\** ok whilst we wait for that -**\** there's been some discussion about fees with the price rise -**\** any thoughts on the fee thing? -**\** i think they are still fine -**\** My thought is that fees will ultimately have to be tied to the blocksize -**\** what will be the price point when they change? -**\** at the moment it's like $0.012 per kb I think -**\** Ideally we would wait for it to settle down a bit -**\** the price -**\** yeah -**\** Too soon for adjustments imo -**\** true -**\** gingeropolous: dropping fees is a hard fork, so ideally we want to bundle it into the October fork or whatever -**\** 1 cent is nothing -**\** You mean fees are in the consensus code -**\** ArticMine: yes - we don't allow 0 fee transactions -**\** We could just calculate the average over the last 6 months -**\** I think ArticMine's point about fees being tied to block size is interesting, as block size goes up, fee per kb declines, linearly I guess -**\** BitcoinErrorLog has been talking about "magic number automation", he might have some thoughts on it too -**\** he's offline atm -**\** jwinterm: yes -**\** fee tied to blocksize - but you can't predict the blocksize when you create a txn to someone -**\** hyc: we can use the median -**\** the tx size -**\** It is because fess are tied to the emission and blocksize via the bock penalty -**\** right, unpenalized max block size -**\** So we could actually use a formula based on emission and block size -**\** So that the min fee corresponds to a low position in the penalty -**\** say around 5% -**\** present! -**\** is anyone aware of another coin using a similar scheme with also using the block size? seems worth looking into. -**\** not that I know of -**\** This only applies to cryptonote -**\** i think it'd be awesome to find a way to do it automatically, as opposed to hardforks -**\** but likely Monero would be first -**\** it sounds good. especially since emission and blocksize are already automatic -**\** ok let's sketch that out and see what we come up with -**\** in the meantime, we need to push 0.9.2 out -**\** I can put something together -**\** I was holding off on it until the meeting -**\** on fees -**\** I'm still hitting SIGBUS on ARMv7 but go ahead with current PRs and don't wait for anything more from me -**\** ok -**\** moneromooo: how are you feeling on an upstream merge to dev? -**\** I don't see my test resolving this soon -**\** the current RPC interface is starting to become a problem for multiple concurrent wallet sessions -**\** I'm waiting for 0.9.2 to be tagged first so that no new patches go there. -**\** ok -**\** (or few anyway) -**\** Why is it a problem ? -**\** The new one seems to be made to be non thread safe fwiw. -**\** moneromooo: Peter Todd and I have hit the issue with scanning a new wallet when other wallets are open -**\** and I don't think we should necessarily waste time trying to optimise an interface that's going away -**\** Oh what does this break ? -**\** it makes it slooooow -**\** Ah, fair enough. Did you try with the 0mq one ? -**\** no - was in the air (literally) :-P -**fluffypony** ponders -**\** oh yes -**\** I would prefer new wallets don't auto-refresh, but I understand why it was added -**\** net_skeleton become Fossa which became Mongoose -**\** which needs to become gone ? -**\** yes -**\** the only licenses they have available are GPL and a commercial license -**\** which doesn't play well with ours -**\** We would have to go GPL -**\** basically we just need a library that plays well with HTTPS, and supports authentication -**\** and is compatible with our license -**\** something to keep eyes out for -**\** next up: ringCT -**\** warptangent: you were chatting to Shen - what's the latest on that? -**\** i've begun to familiarize myself with what will need to be done, and development on that will go on top of the newer database branch -**\** we'll be opening Github issues or Forum threads, either or, for the specific decisions we have to make around things like ring size -**\** a forum thread would work well for the first issue re: floating point or fixed -**\** luigi1114: you had some thoughts on that, iirc? -**\** I do -**\** I feel like I've missed a lot of stuff, somehow. -**\** im still getting woops something went wrong when click on the bell on the forum... not that I need to do much for these topics, but just throwin it out there. -**\** gingeropolous: thanks, will take a look at the error log -**\** What's this about floating point ? -**\** I think a forum or other untimed format would be easier though -**\** it's a decision to be made about the confidential transactions scheme -**\** Alright. First I've heard of it. -**\** it's how many amounts can be represented -**\** size tradeoffs basically -**\** So since I've not seen that conversation nor arguments, I'll just say "floating point is only fine if you really know what you're doing". -**\** it's more a design decision -**\** moneromooo: first you've heard of RingCT, or of the floating point / fixed issue? -**\** fp/fp -**\** the conversation needs to take place in the forum and with Shen's input. moneromooo i only recently learned of it myself. -**\** It has significant economic implications -**\** we're not going to get very far here I agree warptangent -**\** ok - let's create a thread -**\** does anyone want to run with that? -**\** *silence* -**\** lol -**\** crickets -**\** i can -**\** thanks warptangent -**\** i'll let NobleSir know when it's up too -**\** Can I make a general remark? -**\** dEBRUYNE: of course -**\** We should change mixin to ring size or another sufficient alternative -**\** mixin sounds active -**\** which isn´t the case -**\** we were just talking about ringsize just now, in context of RingCT -**\** I know - terminology and binary name changes are going to happen for 1.0 -**\** sounds like ring size already has a meaning that we shouldn't confuse -**\** and making sure flags are all uniform etc. -**\** hyc: Yeah I saw that, I just wanted some confirmation that we are going to change that -**\** certainly with a lot of newcomers coming in it might be confusing -**\** \ and making sure flags are all uniform etc. <= Great -**\** definitely -**\** hyc: I believe they are the same (function at least) -**\** ok, then that's straightforward -**\** ring size is the community agreed replacement for (mixin+1) -**\** well number of bytes in a ringct is different than what's currently mixin count -**\** i think that's hyc's concern -**\** Then we should name them similiar -**\** shouldn´t -**\** \* -**\** yes. I didn't follow ringct closely, but the fact that floating point is even an option means the two are quite different -**\** it's likely the latter is the one most users will even be aware of. -**\** but it's something to consider. -**\** warptangent: Agree, perhaps we could ask NobleSir if he has a sufficient synonym -**\** \ well number of bytes in a ringct is different than what's currently mixin count <= this doesn't parse for me -**\** afaik users don't choose anything with ringCT, though -**\** floating point/exponents/bitsize has nothing to do with ring size and won't be named similarly -**\** luigi1112: just the storage size for a ringct, if referred to as "ring size" could be confusing for those using "ring size" to refer to mixin count -**\** ok -**\** yes the former will/should not be named that way -**\** signature size or something -**\** yeah, i was not aware ring size already was used for something -**\** maybe this isn't the place for the discussion but I would have preferred something other than "ring size" for mixin count. masking factor, blinding factor. -**\** something that actually conveys the purpose. -**\** as hyc mentioned, decoys is actually a good name / descriptor -**\** Agree there. -**\** but it sounds too subterfugey -**\** yell on the reddit thead :) -**\** the thread it still open -**\** lol -**\** anyway not a good place here -**\** ok -**\** or time -**\** hyc: Ring size was just brought up earlier, it was more about the idea of changing it -**\** Just arrived, what the subject? -**\** Another term is fine by me as well -**\** i do like ring size fwiw. -**\** malmenonphome: Changing the term mixin to something else -**\** this is basically a community thing, not a dev thing -**\** @fluffypony not yet, I'll work on osx/linux this weekend and see from there. As for the firmware, I'll request a pull upstream once I've added it to github. They are interested in merging it upstream. -**\** (beyond making sure the name makes sense) -**\** luigi1114: Let´s continue to the next subject then :) -**\** Ah, ok, I agree with ring size as well, but we should think in other languages how it sounds too -**\** masking/blinding factor or decoy is more descriptive, but ring size could be a happy medium between that and not making every user have to feel like a rebel. -**\** ring size is ok for me, if it doesn't convey meaning people will learn and that's a good thing -**\** In Portuguese... Tamanho de anel -**\** right the problem with mixin is that people think it's a typo for the other word -**\** yeah -**\** ok - that's a discussion to have on the reddit thread or wherever -**\** mixin definitely gives the idea, as we've seen, that it requires other active senders -**\** we're not in a position to make a decision on it in this meeting -**\** I agree -**\** any word on the dev branch? as one who has been summarizing these meetings, the can has been kicked twice now. -**\** we can can kick better than bitcoin huh -**\** it was discussed above? -**\** gingeropolous: did you miss part of the meeting? -**\** perhaps. sorry. /me hides -**\** is ok -**\** in the summary you can just be like "the official troll-appointed dev was late" -**\** :-P -**warptangent** wonders who the first dev-appointed troll will be. -**\** hah hah -**\** ok I think that brings the meeting to a close diff --git a/downloads/hashes.txt b/downloads/hashes.txt index 629f00dd..ca210c1c 100644 --- a/downloads/hashes.txt +++ b/downloads/hashes.txt @@ -1,25 +1,27 @@ -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 -This GPG-signed message exists to confirm the SHA sums on Monero binaries. +This GPG-signed message exists to confirm the SHA256 sums on Monero binaries. Please verify the signature against the signature for fluffypony in the source code repository (/utils/gpg_keys). -monero.win.x64.v0-9-1-0.zip: 303840d7fb997b2f1efc280fd19ba84003ecff85 -monero.mac.x64.v0-9-1-0.tar.bz2: d6c776878fd3d47f149fc9be4e76cf2d03d5a725 -monero.linux.x64.v0-9-1-0.tar.bz2: 4149de91c10b56ff091070acca80d233fbd5a797 -monero.freebsd.x64.v0-8-6-6.tar.bz: 9fd0005b697e146a26a0bf9e3cd0c89b978f7fbd +246115b0da133e0203dc78d26bbc82e9b76a178939bff8d4541bf04a02a19854 monero.win.x64.v0-9-3-0.zip +4663222a810ad854da1fc9d665e51252e61ddb1a8f69de3a31ad195386d445a2 monero.win.x86.v0-9-3-0.zip +f471a420485413d5fcb1b19065a3b4e9a68c49596ddd6291787ad34121bad32c monero.mac.x64.v0-9-3-0.tar.bz2 +9e6747b69642389e98ca5f70cec7276f7af7156e5dce95409a8da7cccff5876e monero.linux.x64.v0-9-3-0.tar.bz2 +90c51c4a68f78ac2262a7b5a676f02d43ba7b9b6800b8b150d89980604c969f2 monero.linux.x86.v0-9-3-0.tar.bz2 +c312ba0810bf04ab2e28b61a50de2a83c1c614fd789bab4cacacb716134a7239 monero.linux.arm7.v0-9-3-0.tar.bz2 Riccardo "fluffypony" Spagni -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 -iQEcBAEBAgAGBQJWmTisAAoJEFVDLfMczU/NDQMIAKKYY2/NI5LH4COMIAXRf02x -TTa+veq8job7jnyVI3C+kl2Wtws026CsUHy1TQNrU5krGs5FA77RFrozIIn4Ca7e -su3u0K14hdO8d+bfiPf3n3eh+CTa5/ihbKVf8BannwjI9tyYzjrLSl49rfftdaRP -vpCVyqbApkNzntiIyG/SypGEW9G1b9rQU4RGE0GK836zf4Pu2jz3ZD6Clbc+gGri -/PmLSYBulkcbQ/7TW8Sl0sn+Lj1WF9duVqS/sZiXdws2sT++Lj4LzmNMGDE4SMLe -eYWEu6FrgpmRzLAhqa3pWAOC12bmrINvU8W2/oAXMIPUdyTb3IDJtWhm2KGqJEo= -=3WkU +iQEcBAEBAgAGBQJW8UP6AAoJEFVDLfMczU/NYYIH/i46PXwNyt2ghnpslGXGrMhv +72ozR4OjdkNzl/z1PwcE2lAY8Z8od/OiZRB6zJl77555J+MxrP8rNa1i4fLRMAQn +5hIss+dhy6dRf+Tfgd6sZo6iXE5zmvgeOHgIfdtU6TRUC0ak0TRuFeQsTd8sXUCW +u6bIhRS2Bgo3C/Nj/o4k8zPUBjElc4XQyFFMqaM3PUuG8Ok/j0Nzyd+P0Av+jdfe +4SItOYH13V80ZnqEcp7QKeFKNYQVs7aGKzEMs/QNZvoscuiUA1RStkvwJ9pGfno/ +F0cWnZSzGhYErIRldeQcTwJKIGtk1GcVnZLK1jkjlZeXq7MLtyKDblfctBfUmn8= +=MkuA -----END PGP SIGNATURE----- \ No newline at end of file diff --git a/downloads/index.md b/downloads/index.md index ee96a3d8..ad59ec58 100644 --- a/downloads/index.md +++ b/downloads/index.md @@ -15,7 +15,7 @@ Monero Core consists of several applications, including bitmonerod (the daemon u If you are using Monero Core for the first time you can simply download an appropriate release, and run bitmonerod to get synced up to the network. -Note: the SHA hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). +Note: the SHA256 hashes are listed by the downloads for convenience, but a GPG-signed list of the hashes is at [getmonero.org/downloads/hashes.txt](https://getmonero.org/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys).