Grok 4.3 release
> #1 in caselaw
> #1 in corpfin
> impressive given significantly lower cost per 1m tokens (5-10x less than opus 4.7 and openai 5.5)
Very exciting to see the massive jump in performance in highly detail-oriented applied fields
AI 직접 배워보기 1주일차
혼자만의 힘으로 숏폼영상 자동생성 및 업로드까지 만들어봤네요
이제 뭐든 하고자하면 만들 수 있을거라는 자신감이드네요
영상 퀄리티나 ui같은건 라이브러리가져다 쓰는식으로 보완하고하면 점점더 나아질거라고 생각해요
우선 내일부터 매일 주요이슈10가지를 숏폼영상으로 제작해서 유튜브 틱톡 인스타 x에 업로드될예정입니다
AI 직접 배워보기 3일차
오늘은 claude를 앱에서 쓰는게 아닌 VScode 터미널로 불러서 쓰는 방식을 배워서 적용했다.
기존에 내가 쓰던방식이 얼마나 불편하고 초보적인 방식이었는지 이제야 알았다.
추가로 superpowers도 설치해보고 다양한 기능들을 익혔다.
이러한 기능들과 아이디어를 바탕으로 Claude와 대화하면서 숏폼플랫폼 자동화 프로그램을 작성했다.
완성되면 X에도 같이 올려보겠습니다.
AI 직접 배워보기 2일차
실제 지갑을 연결해서 트레이딩하는건 좀 애를많이 먹었다
먼저 주문까지가는건 금방했는데 주문과정이 자꾸 에러가났다
결국 해결한 방법은 폴리마켓에 api사용에대한 가이드를 클로드에게 던져준 이후였다
여기서 느낀건 특정 메뉴얼이나 가이드,깃헙의 좋은예시를던져주는게 코딩문제를 해결하기 쉬운방법이라는거다
승률이 아주좋진 않지만 원하는조건하에 지속해서 매수 매도가 발생하고있고, 일부 잘못된주문은 클로드에게 보여주고 코드를 다듬어 나가고있다
두번째로 리니지m 다계정 작업장을 위한 모니터분할하여 실시간미러링 클릭 프로그램을 만들었다 아주 만족한다 ㅎㅎ 이렇게필요한걸 하나씩 만들어서쓸수있다는게 놀랍고 이런시대가 온게 신기하다
AI 직접 배워보기 1일차
요즘 X 알고리즘이 클로드를 활용한 자동화와 수익창출로 도배가 되고있다. 더늦기전에 나도 도전해봐야지.
제미나이 그록 gpt로 그냥 질문만 하던 내가, 코딩에 코짜도 모르는 내가 일단 시작해본다!!
제미나이랑 대화하면서 cloude를 활용해서 여러가지 해보기로 다짐했다.
유튜브 자동화, X 자동화, 블로그 자동화
폴리마켓 자동매매
앱개발
웹사이트개발
첫번째로 시도해보는 것은 폴리마켓 자동매매
우선 아무것도 모르는 초짜라서 제미나이랑 대화하면서 하나부터 열까지 물어가면서 진행했다
1. python 설치해보기
2.VS Code설치
3.VS Code에 python 설치하기
4.VS Code에 pip 기능 사용해서 라이브러리 추가해보기
5.Cloude랑 대화해서 코드작성해보기
6.VS Code로 코드 실행해보기
그 결과 단 한시간만에
폴리마켓 데이터 자동으로 가져오기
수립한 전략으로 폴리마켓 모의트레이딩/실시간현황 살펴보기를 완료했다
2일차에는 실제로 지갑을 개설해서 10만원정도 넣고 트레이딩을 시켜봐야겠다.
도전이 궁금하신분들이나 팁을 주실분들은 좋아요 댓글 부탁해요.
Ethereum itself must pass the walkaway test.
Ethereum is meant to be a home for trustless and trust-minimized applications, whether in finance, governance or elsewhere. It must support applications that are more like tools - the hammer that once you buy it's yours - than like services that lose all functionality once the vendor loses interest in maintaining them (or worse, gets hacked or becomes value-extractive). Even when applications do have functionality that depends on a vendor, Ethereum can help reduce those dependencies as much as possible, and protect the user as much as possible in those cases where the dependencies fail.
But building such applications is not possible on a base layer which itself depends on ongoing updates from a vendor in order to continue being usable - even if that "vendor" is the all core devs process. Ethereum the blockchain must have the traits that we strive for in Ethereum's applications. Hence, Ethereum itself must pass the walkaway test.
This means that Ethereum must get to a place where we _can ossify if we want to_. We do not have to stop making changes to the protocol, but we must get to a place where Ethereum's value proposition does not strictly depend on any features that are not in the protocol already.
This includes the following:
* Full quantum-resistance. We should resist the trap of saying "let's delay quantum-resistance until the last possible moment in the name of ekeing out more efficiencies for a while longer". Individual users have that right, but the protocol should not. Being able to say "Ethereum's protocol, as it stands today, is cryptographically safe for a hundred years" is something we should strive to get to as soon as possible, and insist on as a point of pride.
* An architecture that can expand to sufficient scalability. The protocol needs to have the properties that allow it to expand to many thousands of TPS over time, most notably ZK-EVM validation and data sampling through PeerDAS. Ideally, we get to a point where further scaling is done through "parameter only" changes - and ideally _those_ changes are not BPO-style forks, but rather are made with the same validator voting mechanism we use for the gas limit.
* A state architecture that can last decades. This means deciding, and implementing, whatever form of partial statelessness and state expiry will let us feel comfortable letting Ethereum run with thousands of TPS for decades, without breaking sync or hard disk or I/O requirements. It also means future-proofing the tree and storage types to work well with this long-term environment.
* An account model that is general-purpose (this is "full account abstraction": move away from enshrined ECDSA for signature validation)
* A gas schedule that we are confident is free of DoS vulnerabilities, both for execution and for ZK-proving
* A PoS economic model that, with all we have learned over the past half decade of proof of stake in Ethereum and full decade beyond, we are confident can last and remain decentralized for decades, and supports the usefulness of ETH as trustless collateral (eg. in governance-minimized ETH-backed stablecoins)
* A block building model that we are confident will resist centralization pressure and guarantee censorship resistance even in unknown future environments
Ideally, we do the hard work over the next few years, to get to a point where in the future almost all future innovation can happen through client optimization, and get reflected in the protocol through parameter changes. Every year, we should tick off at least one of these boxes, and ideally multiple. Do the right thing once, based on knowledge of what is truly the right thing (and not compromise halfway fixes), and maximize Ethereum's technological and social robustness for the long term.
Ethereum goes hard.
This is the gwei.
A lot of exciting announcements are coming around the WLFI ecosystem and the continued growth of USD1.
Stay tuned and pay attention there’s a lot ahead. 🦅 ☝️