In aiming to make the Rust programming language more suitable for safety-critical software like within automobiles, aviation, and other industries, the Safety-Critical Rust Consortium was announced to...

CryptoMarket and Blockchain News

DAIJOBUとTECHFUNDがパートナーシップを結成。Web3プロジェクトの品質保証とセキュリティ監査を一貫してサポートする新体制について詳しく解説します。

TECHFUNDが大阪・関西万博のシグネチャーパビリオン「null²」に関連し、デジタルヒューマン型ID基盤「Mirrored Body®」にセキュリティ監査を行ったことを発表しました。

YouTube video by Invezz

TECHFUNDが大阪・関西万博のシグネチャーパビリオンでセキュリティ監査を実施。デジタルヒューマンID「Mirrored Body®」の未来に迫ります。

DOVER, DELAWARE, USA, June 12, 2024 – The Rust Foundation, AdaCore, Arm, Ferrous Systems, HighTec EDV-Systeme GmbH, Lynx Software Technologies, OxidOS, TECHFUND, TrustInSoft, Veecle, and Woven by Toyota are thrilled to jointly announce the Safety-Critical Rust Consortium. The primary objective of this group will be to support the responsible use of the Rust programming language in safety-critical software — systems whose failure can impact human life or cause severe environmental or property harm. Safety-Critical Rust Consortium Membership is open to Rust Foundation member organizations and other invitees, such as industry, academic, and legal experts. Work under the consortium will begin with the creation of a public charter and goals, and meeting minutes will be published on an ongoing basis. The Safety-Critical Rust Consortium will liaise with the Rust Project through Rust Foundation Project Directors and members of Rust Project teams. The Consortium’s scope, which will be fully delineated in the charter, may include the development of guidelines, linters, libraries, static analysis tools, formal methods and language subsets to meet industrial and legal requirements. The Consortium’s deliverables will be developed and licensed in a manner compatible with other Rust Project endeavors. The group may further shepherd Rust Foundation-funded implementation work, including grants to existing academic teams or FOSS projects. Any Rust Foundation-funded work will be submitted upstream, licensed as FOSS, and any specifications will be freely available. The group will further attempt to coordinate with and expand on existing safety-critical projects and standards including SAE JA1020. _“This is exciting! I am truly pleased to see the Rust Foundation and anyone in the safety-critical space coming together on this topic,”_ said Graydon Hoare, creator of the Rust programming language. _" Safety is our foremost priority in vehicle software development. Traditionally, achieving the highest levels of safety has been a complex and lengthy endeavor, requiring the use of specialized tools and processes beyond the programming language. We are therefore pleased to collaborate with leading experts in the safety industry to integrate new tools such as Rust into our safety-critical systems,"_ said JF Bastien, Distinguished Engineer at Woven by Toyota. _“Rust has already established itself as a safe and secure programming language with developers in open source, industry and governments. Now is the time to use that momentum towards bringing Rust as a mainstream language in safety-critical areas, providing processes and specifications that allow Rust to be certified in this space,”_ said Joel Marcey, Director of Technology at the Rust Foundation. Below, the founding members of the Safety-Critical Rust Consortium have addressed several anticipated questions about this effort. ## What is “safety-critical”? Rust is already safe! # Programming language safety refers to a language’s ability to prevent errors or undefined behaviors at compile time or runtime. On the other hand, "safety-critical" refers to a system’s ability to operate without causing accidents or catastrophic failures that will result in harm to people, property or the environment. So, while safety-critical systems rely on languages that emphasize safety and security, such as Rust, programming tools are only one component of the overall strategy. ## Which industries are considered safety-critical? # Industries that are particularly concerned with functional safety include transportation (such as automotive, aviation, space), energy, life sciences, and more. Because of their potential impacts, these industries are often regulated, have liability considerations, and are guided by standards such as IEC 61508, ISO 26262, IEC 62304, and DO-178C. These industries have decades of experience delivering products, learning from iterating based on real-world feedback, and improving processes. An ecosystem of tools and tool vendors have evolved, and best practices have been learned to create a safety culture around tooling. ## Why Rust? # Rust offers particular advantages in terms of developer ergonomics, productivity and software quality; however, it lacks a deep and established well of safety-processes and collective industry knowledge of safety-critical systems. Without closing this gap, a developer must primarily rely on best practices and normative precautions, which can limit innovation. Rust developers who stray from the well-trod path can find themselves facing an inquiry were an accident to occur. In these circumstances, anything that seems unusual will be investigated for fault. This risk creates a disincentive to widespread Rust adoption, leaving developers unable to reap all its advantages while potentially facing financial, reputational and moral costs. The gap in safety-critical resources within the Rust programming language ecosystem is also an exciting opportunity. By rapidly incorporating lessons learned from years of careful development and past mistakes in the wider open source ecosystem, Rust can become a valuable component of a safety toolkit adaptable to various safety-critical industries and severity levels. ## What does this development mean for Rust? # Aspiring to meet safety-critical needs has costs, just as aspiring to security or quality needs does. Some of those costs can be distributed across multiple priorities, such as verification and validation through code review, writing a specification, identifying properties of a “software bill of materials,” etc. The Rust programming language can bear some reasonable costs with the participation of interested parties, but such costs cannot be imposed to Rust the ecosystem thoughtlessly. Indeed, a hobby open source project on crates.io cannot suddenly be made safety-critical, cannot be told that lives depend on the project’s correctness, without serious consideration and buy-in from community members. ## Why this effort, under the Rust Foundation? # There are existing efforts in this space, most notably SAE JA1020. The efforts are laudable, and will likely meet the needs of their target audience. However, we hope that a wider effort under the Rust Foundation can meet the needs of the Rust community at large, rather than a subset of industries, groups and/or use cases. Moreover, the needs of specific groups are sometimes at odds with the needs of others in the community. This can either lead to tensions in adopting stringent requirements, or cause friction in the specific groups significantly lagging behind in the evolution of the language and tools surrounding it. By working under the auspices of the Rust Foundation, the Safety-Critical Rust Consortium can minimize the risk of such fracturing. ## How will this group work with the Rust Project? # The expectation is that the Safety-Critical Rust Consortium attracts many participants who are not currently Rust users. The initial group members understand that the Rust Project operates in particular ways and is wary of external entities aggressively promoting their own goals. The hope of the initial group members is to listen to the Rust Project members’ inputs and understand how to best broaden the user base and applicability of Rust without adversely affecting existing Rust users and Rust Project participants. The Safety-Critical Rust Consortium should collaborate with the Rust Project Language Specification Team and the Formal Methods team. It should also perform work as the Rust Project does – through Zulip and virtual meetings with public minutes. The consortium plans to hold its first in person meeting at RustConf 2024 out of a desire to integrate into and work closely with the Rust Project. The Safety-Critical Rust Consortium intends to keep all stakeholders updated on its work, suggesting modification or additions to how the Rust language and libraries are created and addressing how different safety levels adopt the language and libraries. Doing so will create room for a variety of tooling to support safety activities, verification and validation, and quality assurance within Rust. The work would, in turn, create best practices, which can then be discussed with safety assessors and governments to more officially establish the best practices as recommendations. ## What is the expected impact outside of the Rust Foundation and Project? # Work such as SAE’s would not become obsolete through a Safety-Critical Rust Consortium, it would however become narrower in tuning the wider work to their specific audience, after informing the safety-critical Rust group about their needs. The safety-critical Rust Consortium, and the wider Rust Foundation, would then pursue an industry adoption and advocacy role, with users of Rust as well as with external entities such as governments and international standards groups. The Rust Foundation is committed to ensuring that funding and support are available where needed, including both community volunteers and funded initiatives, such as for this safety initiative. ## Why participate? # In short, your help is needed! We want the Safety-Critical Rust Consortium to reflect a wide variety of perspectives, including various safety industries, representatives from standards groups guiding these industries, tooling providers who cater to such industries, and Rust community members from the language and library spaces which are interested in collaboration. ## How can I ask another question and/or get involved? # Interested organizations, individuals, and Rust Foundation Members are invited to get in touch with us via email at contact@rustfoundation.org. * * * ## About the Rust Foundation # The Rust Foundation is an independent nonprofit dedicated to the safety, security, sustainability, and health of the Rust Programming language and the people who use it. Through close partnerships with organizations passionate about Rust and the growing Rust Project and community, the Rust Foundation is helping forge a better open source future with Rust. Visit the Rust Foundation website to learn more. Follow the Rust Foundation on X (formerly known as Twitter) and on LinkedIn.

DOVER, DELAWARE, USA, June 12, 2024 – The Rust Foundation, AdaCore, Arm, Ferrous Systems, HighTec EDV-Systeme GmbH, Lynx Software Technologies, OxidOS, TECHFUND, TrustInSoft, Veecle, and Woven by Toyota are thrilled to jointly announce the Safety-Critical Rust Consortium. The primary objective of this group will be to support the responsible use of the Rust programming language in safety-critical software — systems whose failure can impact human life or cause severe environmental or property harm. Safety-Critical Rust Consortium Membership is open to Rust Foundation member organizations and other invitees, such as industry, academic, and legal experts. Work under the consortium will begin with the creation of a public charter and goals, and meeting minutes will be published on an ongoing basis. The Safety-Critical Rust Consortium will liaise with the Rust Project through Rust Foundation Project Directors and members of Rust Project teams. The Consortium’s scope, which will be fully delineated in the charter, may include the development of guidelines, linters, libraries, static analysis tools, formal methods and language subsets to meet industrial and legal requirements. The Consortium’s deliverables will be developed and licensed in a manner compatible with other Rust Project endeavors. The group may further shepherd Rust Foundation-funded implementation work, including grants to existing academic teams or FOSS projects. Any Rust Foundation-funded work will be submitted upstream, licensed as FOSS, and any specifications will be freely available. The group will further attempt to coordinate with and expand on existing safety-critical projects and standards including SAE JA1020. _“This is exciting! I am truly pleased to see the Rust Foundation and anyone in the safety-critical space coming together on this topic,”_ said Graydon Hoare, creator of the Rust programming language. _" Safety is our foremost priority in vehicle software development. Traditionally, achieving the highest levels of safety has been a complex and lengthy endeavor, requiring the use of specialized tools and processes beyond the programming language. We are therefore pleased to collaborate with leading experts in the safety industry to integrate new tools such as Rust into our safety-critical systems,"_ said JF Bastien, Distinguished Engineer at Woven by Toyota. _“Rust has already established itself as a safe and secure programming language with developers in open source, industry and governments. Now is the time to use that momentum towards bringing Rust as a mainstream language in safety-critical areas, providing processes and specifications that allow Rust to be certified in this space,”_ said Joel Marcey, Director of Technology at the Rust Foundation. Below, the founding members of the Safety-Critical Rust Consortium have addressed several anticipated questions about this effort. ## What is “safety-critical”? Rust is already safe! # Programming language safety refers to a language’s ability to prevent errors or undefined behaviors at compile time or runtime. On the other hand, "safety-critical" refers to a system’s ability to operate without causing accidents or catastrophic failures that will result in harm to people, property or the environment. So, while safety-critical systems rely on languages that emphasize safety and security, such as Rust, programming tools are only one component of the overall strategy. ## Which industries are considered safety-critical? # Industries that are particularly concerned with functional safety include transportation (such as automotive, aviation, space), energy, life sciences, and more. Because of their potential impacts, these industries are often regulated, have liability considerations, and are guided by standards such as IEC 61508, ISO 26262, IEC 62304, and DO-178C. These industries have decades of experience delivering products, learning from iterating based on real-world feedback, and improving processes. An ecosystem of tools and tool vendors have evolved, and best practices have been learned to create a safety culture around tooling. ## Why Rust? # Rust offers particular advantages in terms of developer ergonomics, productivity and software quality; however, it lacks a deep and established well of safety-processes and collective industry knowledge of safety-critical systems. Without closing this gap, a developer must primarily rely on best practices and normative precautions, which can limit innovation. Rust developers who stray from the well-trod path can find themselves facing an inquiry were an accident to occur. In these circumstances, anything that seems unusual will be investigated for fault. This risk creates a disincentive to widespread Rust adoption, leaving developers unable to reap all its advantages while potentially facing financial, reputational and moral costs. The gap in safety-critical resources within the Rust programming language ecosystem is also an exciting opportunity. By rapidly incorporating lessons learned from years of careful development and past mistakes in the wider open source ecosystem, Rust can become a valuable component of a safety toolkit adaptable to various safety-critical industries and severity levels. ## What does this development mean for Rust? # Aspiring to meet safety-critical needs has costs, just as aspiring to security or quality needs does. Some of those costs can be distributed across multiple priorities, such as verification and validation through code review, writing a specification, identifying properties of a “software bill of materials,” etc. The Rust programming language can bear some reasonable costs with the participation of interested parties, but such costs cannot be imposed to Rust the ecosystem thoughtlessly. Indeed, a hobby open source project on crates.io cannot suddenly be made safety-critical, cannot be told that lives depend on the project’s correctness, without serious consideration and buy-in from community members. ## Why this effort, under the Rust Foundation? # There are existing efforts in this space, most notably SAE JA1020. The efforts are laudable, and will likely meet the needs of their target audience. However, we hope that a wider effort under the Rust Foundation can meet the needs of the Rust community at large, rather than a subset of industries, groups and/or use cases. Moreover, the needs of specific groups are sometimes at odds with the needs of others in the community. This can either lead to tensions in adopting stringent requirements, or cause friction in the specific groups significantly lagging behind in the evolution of the language and tools surrounding it. By working under the auspices of the Rust Foundation, the Safety-Critical Rust Consortium can minimize the risk of such fracturing. ## How will this group work with the Rust Project? # The expectation is that the Safety-Critical Rust Consortium attracts many participants who are not currently Rust users. The initial group members understand that the Rust Project operates in particular ways and is wary of external entities aggressively promoting their own goals. The hope of the initial group members is to listen to the Rust Project members’ inputs and understand how to best broaden the user base and applicability of Rust without adversely affecting existing Rust users and Rust Project participants. The Safety-Critical Rust Consortium should collaborate with the Rust Project Language Specification Team and the Formal Methods team. It should also perform work as the Rust Project does – through Zulip and virtual meetings with public minutes. The consortium plans to hold its first in person meeting at RustConf 2024 out of a desire to integrate into and work closely with the Rust Project. The Safety-Critical Rust Consortium intends to keep all stakeholders updated on its work, suggesting modification or additions to how the Rust language and libraries are created and addressing how different safety levels adopt the language and libraries. Doing so will create room for a variety of tooling to support safety activities, verification and validation, and quality assurance within Rust. The work would, in turn, create best practices, which can then be discussed with safety assessors and governments to more officially establish the best practices as recommendations. ## What is the expected impact outside of the Rust Foundation and Project? # Work such as SAE’s would not become obsolete through a Safety-Critical Rust Consortium, it would however become narrower in tuning the wider work to their specific audience, after informing the safety-critical Rust group about their needs. The safety-critical Rust Consortium, and the wider Rust Foundation, would then pursue an industry adoption and advocacy role, with users of Rust as well as with external entities such as governments and international standards groups. The Rust Foundation is committed to ensuring that funding and support are available where needed, including both community volunteers and funded initiatives, such as for this safety initiative. ## Why participate? # In short, your help is needed! We want the Safety-Critical Rust Consortium to reflect a wide variety of perspectives, including various safety industries, representatives from standards groups guiding these industries, tooling providers who cater to such industries, and Rust community members from the language and library spaces which are interested in collaboration. ## How can I ask another question and/or get involved? # Interested organizations, individuals, and Rust Foundation Members are invited to get in touch with us via email at contact@rustfoundation.org. * * * ## About the Rust Foundation # The Rust Foundation is an independent nonprofit dedicated to the safety, security, sustainability, and health of the Rust Programming language and the people who use it. Through close partnerships with organizations passionate about Rust and the growing Rust Project and community, the Rust Foundation is helping forge a better open source future with Rust. Visit the Rust Foundation website to learn more. Follow the Rust Foundation on X (formerly known as Twitter) and on LinkedIn.

Tiger's last fund did well with investmetments in OpenAI, Waymo and Databricks. But it warns investors that AI valuations are already 'elevated.'

TMV said the new funding will seed companies that want to apply new technologies to the maritime industry, shipbuilding and related infrastructure.

With a new feasibility study, GitHub’s developer policy team is building a coalition of policymakers and industry to close the maintenance funding gap.

新たな聖地巡礼プラットフォーム『聖地巡礼ノートピア』のβ版がリリース。ファン同士の交流を促進し、地域活性化を図ります。

新しく登場した『聖地巡礼ノートピア』は、アニメやマンガの舞台を訪れたファンが記録を残し地域を支援するサービスです。GPS機能を活かした新体験をぜひ体験してみてください。

GUILD株式会社のプレスリリース 開発・セキュリティ監査・グロース支援を包括的にカバーし、Web3プロジェクトの加速を支援 「LINE Mini Dapp」などブロックチェーン・Web3開発支援を展開するGUILD株式 ...

アニメ・マンガの舞台を巡ってファン同士の交流と地域活性化を促す、新たな観光DXサービス誕生 株式会社TECHFUNDのプレスリリース 「起業家の可能性を最大化する！」をミッションに掲げる株式会社TECHFUND(所在地： ...

GUILDとTECHFUNDの提携により、Web3プロジェクトの開発からセキュリティまでを一元的に支援。安全で堅牢なサービスの実現へ。

[TECHFUND Inc.] [画像1: https://prcdn.freetls.fastly.net/release_image/22017/59/22017-59-9e24fb54f96e17165a3895f49f28d8f5-1920x1280.png?width=536&quality=85%2C75&format=jpeg&auto=webp&fit=bounds&am...

# TECHFUND、大阪・関西万博シグネチャーパビリオン「null²」に協賛提供される「Mirrored Body®」に対しセキュリティ監査を実施（2025年） 株式会社TECHFUND（東京都渋...

　スマホを、もっと楽しく快適に使うには、アプリを活用しよう。本コーナーでは、続々登場する旬なアプリの中から編集部が厳選した、スマホユーザー必携の“てっぱん”アプリをご紹介します！ ◇　　　◇　　　◇ アプリ名：　offu開発者：　株式会社TECHFUND価格：　無料対応OS：　iOS、Androidカテゴリ：　ライフ 　1日の疲れを癒やすのに欠かせないお風呂。毎日入浴するのが面倒に感じる時もあるかもしれないけれど、お風呂に入ればおトクな特典がもらえる、となれば気持ちも変わってくるのではないだろうか。そんな入浴が楽しみになるサービス「offu」とは？ 入浴のログを記録できる「offu」 連続入浴達成でスパ ラクーアが割引または無料に 　単に入浴の記録ができて、動物イラストがゲットできる、というだけではない。10日間連続でウチ風呂に入った記録を残せば、東京ドーム 天然温泉スパ ラクーアで利用できる500円引きクーポンが先着200名限定でもらえる。 　また、30日間連続でウチ風呂かソト風呂に入れば、同施設のペア招待チケットが抽選で当たる。 　毎日ちゃんと入浴すれば、そのご褒美がもらえるということで、ついつい入浴をサボりたくなってしまう人はモチベーションアップにぜひとも役立てたいサービスだ。 　今ならユーザー登録するだけでスパ ラクーアが200円引きになるクーポンも配布中で、これも早い者勝ちだ。 過去の入浴記録を一覧することも可能 何度も入浴することでお得なクーポンをゲットできることも 続きを見る 🧠 編集部の感想： 「offu」は入浴を楽しむための新しいアプローチで、特典があることで毎日の入浴を促進するのが素晴らしいですね。記録をつけることで自分の習慣も見える化され、モチベーションにもつながるのが良いです。忙しい日常の中で、リフレッシュを意識するきっかけになるアプリだと思います。

日々の入浴やサウナ。それは多くの人にとって、一日の疲れを癒し、心身をリフレッシュするための大切な時間だろう。この身近な習慣が、最新テクノロジーと結びつくことで、新たな価値を生み出そうとしている。 株式会社TECHFUNDは、東京ドーム天然温泉 スパ ラクーアを運営する株式会社東京ドームと共同で「offu研究プロジェクト」を発足。 その第一弾として、入浴・サウナ習慣を記録・可視化するアプリ『offu（オフ）』のβ版をリリースした。このアプリは、私たちの入浴体験をどのように変え、ウェルビーイングに貢献するのだろうか。 NFTが入浴の証に。楽しみながら続けるセルフケア習慣 このアプリは、自宅での湯船やシャワー、温浴施設での岩盤浴、サウナ、ボディケアなど、日々の入浴習慣を記録し可視化するもの。 リリースによれば、“入浴前にアプリ上でスイッチをオフにする体験は、ココロとカラダのスイッチが“offu - オフ - ”に切り替わる実感を持つ手助けとなり、慣れると癖になる気持ちよさがあります”……とのことだ。 © 株式会社TECHFUND © 株式会社TECHFUND 『offu』の最もユニークな点は、日々の入浴記録がブロックチェーン上に刻まれ、世界に一つだけの「入浴証明書＝オフログ」としてNFTがもらえる仕組みだ。 自宅での湯船やシャワー、温浴施設での岩盤浴、サウナ、ボディケアなど、あらゆる入浴習慣を美しいデザインで記録し、可視化する。入浴前にアプリ上でスイッチをオフにするという行為は、心と体のスイッチを意識的に「オフ」に切り替える体験を促し、リラックス効果を高める手助けとなる。 この「入浴証明書」を集めることで、ユーザーは加盟店の温浴施設で使えるお得な割引クーポンや限定グッズといった特典を得られる。まさに、日々のセルフケアがお得な体験へと繋がるわけだ。 さらに、入浴証明書には全16種類のユニークなリラックス動物「オフナイキモノ」が描かれており、コレクションする楽しみも提供する。この「オフナイキモノ」のイラストは、2024年8月から10月にかけてスパ ラクーアとのコラボレーションを担当したイラストレーター、越前菜都子氏が手がけ、リラックス体験を彩る。 このプロジェクトの背景には、ストレス社会の進行と多様化する働き方による心身への負担増という、世界共通の社会課題がある。 入浴や温浴が心身に与えるポジティブな影響は古くから知られているものの、その具体的なメカニズムや効果を科学的に明らかにする取り組みは十分ではなかった。 「offu研究プロジェクト」は、温浴習慣がもたらすリラックス効果に着目し、日々の入浴習慣と心身の健康との相関を明らかにすることを目指している。そして、入浴という行為を日常の一部から、心と体を整える重要なセルフケア手段へと昇華させることに挑戦する。 © 株式会社TECHFUND © 株式会社TECHFUND スパ ラクーアで実証実験開始「お風呂文化」を日本から世界へ アプリの可能性を具体的に検証するため、2025年5月から7月にかけて、東京ドーム天然温泉 スパ ラクーアにて、このwebアプリを活用した施設導入の実証実験が実施される。 期間中は『offu』を通じて入浴履歴に基づく「入浴証明書」を提示することで、特典クーポンを受けられるキャンペーンも予定されている。 例えば、βアプリ登録キャンペーンでは、先着1,000名にスパ ラクーアで使える200円割引クーポンがプレゼントされる。また、「ウチ風呂10日間チャレンジ」では、自宅での入浴証明書を10日間分集めると、先着200名に500円割引クーポンが進呈。 © 株式会社TECHFUND © 株式会社TECHFUND さらに、入浴証明書には全16種類のオリジナルキャラクター「オフナイキモノ」が描かれており、これらを6種類集めるとスパ ラクーアのオリジナルメッシュポーチがもらえたり、ウチ風呂・ソト風呂問わず30日間入浴証明書を集めると抽選でスパ ラクーアのペアチケットが当たるなど、多彩な企画が用意されている。 © 株式会社TECHFUND © 株式会社TECHFUND © 株式会社TECHFUND TECHFUNDは「起業家の可能性を最大化する」をミッションに掲げ、テクノロジーアクセラレーターとして多くのスタートアップや社内起業家を支援してきた実績を持つ。今回の『offu』は、同社が培ってきた技術力と、日本の伝統文化である入浴を組み合わせることで生まれる新しい価値提案と言えるだろう。 日々の何気ない入浴が、ブロックチェーンに記録され、特典となり、さらには健康増進にも繋がるかもしれない。 『offu』の登場は、テクノロジーが私たちの生活習慣をより豊かで意味のあるものへと変えていく可能性を示している。この小さなアプリが、日本の入浴文化にどのような革新をもたらし、世界のウェルビーイングに貢献していくのか、今後の展開が注目される。 © 株式会社TECHFUND アプリの詳細については、以下の『offu』β版公式ホームページから。  公式ホームページ： Top image: © 株式会社TECHFUND Source link